NetSight

Security Dashboard

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

Reset
73 matching advisories · page 2 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2021-45116 Information disclosure in Django pip · Django 2022-01-05 high7.5 CVE-2021-45115 Denial-of-service in Django pip · Django 2022-01-05 high7.3 CVE-2021-44420 Potential bypass of an upstream access control based on URL paths in Django pip · Django 2021-12-08 high7.5 CVE-2021-33571 Django Access Control Bypass possibly leading to SSRF, RFI, and LFI attacks pip · Django 2021-06-08 high7.5 CVE-2021-31542 Path Traversal in Django pip · Django 2021-05-05 high7.4 CVE-2020-35681 Django Channels leakage of session identifiers using legacy AsgiHandler pip · channels 2021-02-22 high7.5 CVE-2020-24584 Django Incorrect Default Permissions pip · django 2020-09-01 high7.5 CVE-2020-24583 Django Incorrect Default Permissions pip · Django 2020-09-01 high5.9 CVE-2020-13254 Data leakage via cache key collision in Django pip · Django 2020-06-03 high8.8 CVE-2020-9402 SQL injection in Django pip · Django 2020-03-05 high6.5 CVE-2019-19118 Django allows unintended model editing pip · Django 2019-12-02 high7.5 CVE-2019-14235 Uncontrolled Recursion in Django pip · Django 2019-08-02 high7.5 CVE-2019-14233 Django Denial-of-service in strip_tags() pip · Django 2019-08-02 high7.5 CVE-2019-14232 Django Denial-of-service in django.utils.text.Truncator pip · Django 2019-08-02 high7.5 CVE-2019-6975 Uncontrolled Memory Consumption in Django pip · Django 2019-02-11 high6.5 CVE-2019-3498 Improper Input Validation in Django pip · Django 2019-01-09 high7.5 CVE-2018-6188 Django vulnerable to information leakage in AuthenticationForm pip · django, pip · Django 2018-02-05 high7.5 CVE-2016-7401 Django CSRF Protection Bypass pip · django 2016-10-03 high7.4 CVE-2016-2512 Django XSS Vulnerability pip · django, pip · Django 2016-04-08 high5.5 CVE-2016-2048 Django Access Restrictions Bypass pip · django 2016-02-08 high7.5 CVE-2015-5145 Django ReDoS in validators.URLValidator pip · Django 2015-07-14 high7.5 CVE-2015-5144 Django Vulnerable to HTTP Response Splitting Attack pip · django, pip · Django 2015-07-14 high7.5 CVE-2015-5143 Django Denial-of-service by filling session store pip · django, pip · Django 2015-07-14 high7.5 CVE-2015-2316 Django Denial-of-service possibility with strip_tags pip · Django 2015-03-25 high7.5 CVE-2015-0222 Django database denial-of-service with ModelMultipleChoiceField pip · Django 2015-01-16 high7.5 CVE-2015-0221 Django DoS in django.views.static.serve pip · django, pip · Django 2015-01-16 high7.5 CVE-2014-0481 Django denial of service via file upload naming pip · django, pip · Django 2014-08-26 high7.5 CVE-2014-0480 Django Incorrectly Validates URLs pip · django, pip · Django 2014-08-26 high7.5 CVE-2014-3730 Django Allows Open Redirects pip · Django 2014-05-16 high7.5 CVE-2014-0473 Django Reuses Cached CSRF Token pip · django, pip · Django 2014-04-23

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.