NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
66 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2022-25263 JetBrains TeamCity before 2021.2.3 was vulnerable to OS command injection in the Agent Push feature configuration. jetbrains · teamcity 2022-02-25 critical9.8 CVE-2022-25262 In JetBrains Hub before 2022.1.14434, SAML request takeover was possible. jetbrains · hub 2022-02-25 critical9.1 CVE-2022-25260 JetBrains Hub before 2021.1.14276 was vulnerable to blind Server-Side Request Forgery (SSRF). jetbrains · hub 2022-02-25 critical9.8 CVE-2022-24442 JetBrains YouTrack before 2021.4.40426 was vulnerable to SSTI (Server-Side Template Injection) via FreeMarker templates. jetbrains · youtrack 2022-02-25 critical9.8 CVE-2022-24340 In JetBrains TeamCity before 2021.2.1, XXE during the parsing of the configuration file was possible. jetbrains · teamcity 2022-02-25 critical9.8 CVE-2022-24331 In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible. jetbrains · teamcity 2022-02-25 critical9.8 CVE-2021-45977 JetBrains IntelliJ IDEA 2021.3.1 Preview, IntelliJ IDEA 2021.3.1 RC, PyCharm Professional 2021.3.1 RC, GoLand 2021.3.1, PhpStorm 2021.3.1 Preview, PhpStorm 202… jetbrains · clion, jetbrains · goland, jetbrains · intellij_idea +4 2022-02-25 critical9.8 CVE-2021-43202 In JetBrains TeamCity before 2021.1.3, the X-Frame-Options header is missing in some cases. jetbrains · teamcity 2021-11-30 critical9.8 CVE-2021-43200 In JetBrains TeamCity before 2021.1.2, permission checks in the Agent Push functionality were insufficient. jetbrains · teamcity 2021-11-09 critical9.8 CVE-2021-43193 In JetBrains TeamCity before 2021.1.2, remote code execution via the agent push functionality is possible. jetbrains · teamcity 2021-11-09 critical9.8 CVE-2021-43185 JetBrains YouTrack before 2021.3.23639 is vulnerable to Host header injection. jetbrains · youtrack 2021-11-09 critical9.8 CVE-2021-43183 In JetBrains Hub before 2021.1.13690, the authentication throttling mechanism could be bypassed. jetbrains · hub 2021-11-09 critical9.1 CVE-2021-37549 In JetBrains YouTrack before 2021.1.11111, sandboxing in workflows was insufficient. jetbrains · youtrack 2021-08-06 critical9.8 CVE-2021-37544 In JetBrains TeamCity before 2020.2.4, there was an insecure deserialization. jetbrains · teamcity 2021-08-06 critical9.8 CVE-2021-36209 In JetBrains Hub before 2021.1.13389, account takeover was possible during password reset. jetbrains · hub 2021-08-06 critical9.8 CVE-2021-31915 In JetBrains TeamCity before 2020.2.4, OS command injection leading to remote code execution was possible. jetbrains · teamcity 2021-05-11 critical9.8 CVE-2021-31914 In JetBrains TeamCity before 2020.2.4 on Windows, arbitrary code execution on TeamCity Server was possible. jetbrains · teamcity 2021-05-11 critical9.8 CVE-2021-31897 In JetBrains WebStorm before 2021.1, code execution without user confirmation was possible for untrusted projects. jetbrains · webstorm 2021-05-11 critical9.8 CVE-2021-31909 In JetBrains TeamCity before 2020.2.3, argument injection leading to remote code execution was possible. jetbrains · teamcity 2021-05-11 critical9.8 CVE-2021-25770 In JetBrains YouTrack before 2020.5.3123, server-side template injection (SSTI) was possible, which could lead to code execution. jetbrains · youtrack 2021-02-03 critical9.8 CVE-2020-25207 JetBrains ToolBox before version 1.18 is vulnerable to Remote Code Execution via a browser protocol handler. jetbrains · toolbox 2020-11-16 critical9.8 CVE-2020-11796 In JetBrains Space through 2020-04-22, the password authentication implementation was insecure. jetbrains · space 2020-04-22 critical9.8 CVE-2020-11690 In JetBrains IntelliJ IDEA before 2020.1, the license server could be resolved to an untrusted host in some cases. jetbrains · intellij_idea 2020-04-22 critical9.8 CVE-2019-18364 In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution. jetbrains · teamcity 2019-10-31 critical9.8 CVE-2019-12736 JetBrains Ktor framework before 1.2.0-rc does not sanitize the username provided by the user for the LDAP protocol, leading to command injection. jetbrains · ktor 2019-10-02 critical9.8 CVE-2019-12157 In JetBrains UpSource versions before 2018.2 build 1293, there is credential disclosure via RPC commands. jetbrains · teamcity, jetbrains · upsource 2019-10-02 critical9.8 CVE-2019-15039 An issue was discovered in JetBrains TeamCity 2018.2.4. jetbrains · teamcity 2019-10-01 critical9.8 CVE-2019-12852 An SSRF attack was possible on a JetBrains YouTrack server. jetbrains · youtrack 2019-07-03 critical9.8 CVE-2019-9873 In several versions of JetBrains IntelliJ IDEA Ultimate, creating Task Servers configurations leads to saving a cleartext unencrypted record of the server cred… jetbrains · intellij_idea 2019-07-03 critical9.8 CVE-2019-9823 In several JetBrains IntelliJ IDEA versions, creating remote run configurations of JavaEE application servers leads to saving a cleartext record of the server … jetbrains · intellij_idea 2019-07-03

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.