NetSight

Security Dashboard

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

Reset
122 matching advisories · page 4 of 5Index updated 11 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2024-41826 In JetBrains TeamCity before 2024.07 stored XSS was possible on Show Connection page jetbrains · teamcity 2024-07-22 low3.5 CVE-2024-38507 In JetBrains Hub before 2024.2.34646 stored XSS via project description was possible jetbrains · hub 2024-06-18 low3.5 CVE-2024-35300 In JetBrains TeamCity between 2024.03 and 2024.03.1 several stored XSS in the available updates page were possible jetbrains · teamcity 2024-05-16 low2.8 CVE-2024-24940 In JetBrains IntelliJ IDEA before 2023.3.3 path traversal was possible when unpacking archives jetbrains · intellij_idea 2024-02-06 low3.3 CVE-2024-24939 In JetBrains Rider before 2023.3.3 logging of environment variables containing secret values was possible jetbrains · rider 2024-02-06 low3.5 CVE-2023-43566 In JetBrains TeamCity before 2023.05.4 stored XSS was possible during nodes configuration jetbrains · teamcity 2023-09-19 low3.5 CVE-2023-41250 In JetBrains TeamCity before 2023.05.3 reflected XSS was possible during user registration jetbrains · teamcity 2023-08-25 low3.3 CVE-2023-38069 In JetBrains IntelliJ IDEA before 2023.1.4 license dialog could be suppressed in certain cases jetbrains · intellij_idea 2023-07-12 low3.3 CVE-2023-34339 In JetBrains Ktor before 2.3.1 headers containing authentication data could be added to the exception's message jetbrains · ktor 2023-06-01 low3.3 CVE-2022-48435 In JetBrains PhpStorm before 2023.1 source code could be logged in the local idea.log file jetbrains · phpstorm 2023-04-04 low3.9 CVE-2022-46827 In JetBrains IntelliJ IDEA before 2022.3 an XXE attack leading to SSRF via requests to custom plugin repositories was possible. jetbrains · intellij_idea 2022-12-08 low3.5 CVE-2022-45471 In JetBrains Hub before 2022.3.15181 Throttling was missed when sending emails to a particular email address jetbrains · hub 2022-11-18 low2.2 CVE-2022-44646 In JetBrains TeamCity version before 2022.10, no audit items were added upon editing a user's settings jetbrains · teamcity 2022-11-03 low2.7 CVE-2022-44622 In JetBrains TeamCity version between 2021.2 and 2022.10 access permissions for secure token health items were excessive jetbrains · teamcity 2022-11-03 low3.2 CVE-2022-38133 In JetBrains TeamCity before 2022.04.3 the private SSH key could be written to the server log in some cases jetbrains · teamcity 2022-08-10 low3.6 CVE-2022-37010 In JetBrains IntelliJ IDEA before 2022.2 email address validation in the "Git User Name Is Not Defined" dialog was missed jetbrains · intellij_idea 2022-07-28 low3.9 CVE-2022-37009 In JetBrains IntelliJ IDEA before 2022.2 local code execution via a Vagrant executable was possible jetbrains · intellij_idea 2022-07-28 low3.5 CVE-2022-34894 In JetBrains Hub before 2022.2.14799, insufficient access control allowed the hijacking of untrusted services jetbrains · hub 2022-07-01 low3.7 CVE-2022-29929 In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible jetbrains · teamcity 2022-05-12 low3.0 CVE-2022-29820 In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible jetbrains · pycharm 2022-04-28 low3.9 CVE-2022-29818 In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed jetbrains · intellij_idea 2022-04-28 low3.9 CVE-2022-29817 In JetBrains IntelliJ IDEA before 2022.1 reflected XSS via error messages in internal web server was possible jetbrains · intellij_idea 2022-04-28 low2.8 CVE-2022-29816 In JetBrains IntelliJ IDEA before 2022.1 HTML injection into IDE messages was possible jetbrains · intellij_idea 2022-04-28 low2.3 CVE-2022-29812 In JetBrains IntelliJ IDEA before 2022.1 notification mechanisms about using Unicode directionality formatting characters were insufficient jetbrains · intellij_idea 2022-04-28 low3.3 CVE-2022-29035 In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations jetbrains · ktor 2022-04-11 low2.7 CVE-2021-31906 In JetBrains TeamCity before 2020.2.2, audit logs were not sufficient when an administrator uploaded a file. jetbrains · teamcity 2021-05-11 low3.3 CVE-2021-26309 Information disclosure in the TeamCity plugin for IntelliJ before 2020.2.2.85899 was possible because a local temporary file had Insecure Permissions. jetbrains · teamcity 2021-05-11 low3.8 CVE-2021-25775 In JetBrains TeamCity before 2020.2.1, the server admin could create and see access tokens for any other users. jetbrains · teamcity 2021-02-03 low2.5 CVE-2021-25755 In JetBrains Code With Me before 2020.3, an attacker on the local network, knowing a session ID, could get access to the encrypted traffic. jetbrains · code_with_me 2021-02-03 low3.3 CVE-2020-24366 Sensitive information could be disclosed in the JetBrains YouTrack application before 2020.2.0 for Android via application backups. jetbrains · youtrack 2020-11-16

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.