NetSight

Security Dashboard

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

Reset
280 matching advisories · page 8 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2021-43180 In JetBrains Hub before 2021.1.13690, information disclosure via avatar metadata is possible. jetbrains · hub 2021-11-09 high7.5 CVE-2021-43203 In JetBrains Ktor before 1.6.4, nonce verification during the OAuth2 authentication process is implemented improperly. jetbrains · ktor 2021-11-09 high7.5 CVE-2021-43196 In JetBrains TeamCity before 2021.1, information disclosure via the Docker Registry connection dialog is possible. jetbrains · teamcity 2021-11-09 high7.3 CVE-2021-43189 In JetBrains YouTrack Mobile before 2021.2, access token protection on Android is incomplete. jetbrains · youtrack_mobile 2021-11-09 high7.3 CVE-2021-43188 In JetBrains YouTrack Mobile before 2021.2, access token protection on iOS is incomplete. jetbrains · youtrack_mobile 2021-11-09 high7.5 CVE-2021-37553 In JetBrains YouTrack before 2021.2.16363, an insecure PRNG was used. jetbrains · youtrack 2021-08-06 high7.5 CVE-2021-37550 In JetBrains YouTrack before 2021.2.16363, time-unsafe comparisons were used. jetbrains · youtrack 2021-08-06 high7.5 CVE-2021-37548 In JetBrains TeamCity before 2021.1, passwords in cleartext sometimes could be stored in VCS. jetbrains · teamcity 2021-08-06 high7.5 CVE-2021-37545 In JetBrains TeamCity before 2021.1.1, insufficient authentication checks for agent requests were made. jetbrains · teamcity 2021-08-06 high8.8 CVE-2021-37543 In JetBrains RubyMine before 2021.1.1, code execution without user confirmation was possible for untrusted projects. jetbrains · rubymine 2021-08-06 high7.5 CVE-2021-31913 In JetBrains TeamCity before 2020.2.3, insufficient checks of the redirect_uri were made during GitHub SSO token exchange. jetbrains · teamcity 2021-05-11 high8.8 CVE-2021-31912 In JetBrains TeamCity before 2020.2.3, account takeover was potentially possible during a password reset. jetbrains · teamcity 2021-05-11 high7.5 CVE-2021-31910 In JetBrains TeamCity before 2020.2.3, information disclosure via SSRF was possible. jetbrains · teamcity 2021-05-11 high7.5 CVE-2021-31898 In JetBrains WebStorm before 2021.1, HTTP requests were used instead of HTTPS. jetbrains · webstorm 2021-05-11 high7.5 CVE-2021-30482 In JetBrains UpSource before 2020.1.1883, application passwords were not revoked correctly jetbrains · upsource 2021-05-11 high7.5 CVE-2021-31905 In JetBrains YouTrack before 2020.6.8801, information disclosure in an issue preview was possible. jetbrains · youtrack 2021-05-11 high7.5 CVE-2021-31902 In JetBrains YouTrack before 2020.6.6600, access control during the exporting of issues was implemented improperly. jetbrains · youtrack 2021-05-11 high7.5 CVE-2021-31901 In JetBrains Hub before 2021.1.13079, two-factor authentication wasn't enabled properly for the All Users group. jetbrains · hub 2021-05-11 high8.8 CVE-2021-31899 In JetBrains Code With Me bundled to the compatible IDEs before version 2021.1, the client could execute code in read-only mode. jetbrains · code_with_me 2021-05-11 high7.5 CVE-2021-30504 In JetBrains IntelliJ IDEA before 2021.1, DoS was possible because of unbounded resource allocation. jetbrains · intellij_idea 2021-05-11 high7.5 CVE-2021-30006 In IntelliJ IDEA before 2020.3.3, XXE was possible, leading to information disclosure. jetbrains · intellij_idea 2021-05-11 high7.8 CVE-2021-30005 In JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the project from VCS. jetbrains · pycharm 2021-05-11 high7.8 CVE-2021-29263 In JetBrains IntelliJ IDEA 2020.3.3, local code execution was possible because of insufficient checks when getting the project from VCS. jetbrains · intellij_idea 2021-05-11 high7.5 CVE-2021-26310 In the TeamCity IntelliJ plugin before 2020.2.2.85899, DoS was possible. jetbrains · teamcity 2021-05-11 high7.5 CVE-2021-25776 In JetBrains TeamCity before 2020.2, an ECR token could be exposed in a build's parameters. jetbrains · teamcity 2021-02-03 high7.5 CVE-2021-25769 In JetBrains YouTrack before 2020.4.6808, the YouTrack administrator wasn't able to access attachments. jetbrains · youtrack 2021-02-03 high8.8 CVE-2021-25765 In JetBrains YouTrack before 2020.4.4701, CSRF via attachment upload was possible. jetbrains · youtrack 2021-02-03 high7.8 CVE-2021-25758 In JetBrains IntelliJ IDEA before 2020.3, potentially insecure deserialization of the workspace model could lead to local code execution. jetbrains · intellij_idea 2021-02-03 high7.5 CVE-2020-35667 JetBrains TeamCity Plugin before 2020.2.85695 SSRF. jetbrains · teamcity 2021-02-03 high7.5 CVE-2020-27623 JetBrains IdeaVim before version 0.58 might have caused an information leak in limited circumstances. jetbrains · ideavim 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.