NetSight

Security Dashboard

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

Reset
61 matching advisories · page 2 of 3Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.9 CVE-2021-23336 The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to W… python · python, fedoraproject · fedora, debian · debian_linux +9 2021-02-15 medium5.3 CVE-2021-3281 Django Directory Traversal via archive.extract pip · django 2021-02-02 medium6.1 CVE-2020-13596 XSS in Django pip · Django 2020-06-03 medium5.3 CVE-2019-12781 Django Incorrect HTTP detection with reverse-proxy connecting via HTTPS pip · Django 2019-07-01 medium6.1 CVE-2019-12308 An issue was discovered in Django 1.11 before 1.11.21, 2.1 before 2.1.9, and 2.2 before 2.2.2. pip · Django 2019-06-03 medium4.9 CVE-2018-16984 Django allows unprivileged users to read the password hashes of arbitrary accounts pip · django 2018-10-02 medium6.1 CVE-2018-14574 Django open redirect pip · django, pip · Django 2018-08-03 medium5.3 CVE-2018-7537 Django Denial-of-service possibility in truncatechars_html and truncatewords_html template filters pip · django 2018-03-09 medium5.3 CVE-2018-7536 Django denial-of-service possibility in urlize and urlizetrunc template filters pip · Django 2018-03-09 medium6.1 CVE-2017-12794 Django vulnerable to XSS on 500 pages pip · Django 2017-09-07 medium6.1 CVE-2017-7234 Django open redirect pip · django 2017-04-04 medium6.1 CVE-2017-7233 Django open redirect and possible XSS attack via user-supplied numeric redirect URLs pip · Django 2017-04-04 medium6.1 CVE-2016-6186 Django Cross-site scripting Vulnerability pip · django 2016-08-05 medium2.8 CVE-2015-8213 Django settings leak in date template filter pip · django, pip · Django 2015-12-07 medium7.5 CVE-2015-5964 Denial-of-service possibility in logout() view by filling session store pip · Django 2015-08-24 medium7.5 CVE-2015-5963 Django denial of service via empty session record creation pip · Django 2015-08-24 medium7.5 CVE-2015-3982 Django allows user sessions hijacking via an empty string in the session key pip · Django 2015-06-02 medium6.1 CVE-2015-2317 Django cross-site scripting (XSS) attack via user-supplied redirect URLs pip · Django 2015-03-25 medium6.1 CVE-2015-2241 Django Cross-site Scripting Vulnerability pip · django 2015-03-12 medium6.1 CVE-2015-0220 Django Cross-site Scripting Vulnerability pip · django, pip · Django 2015-01-16 medium5.3 CVE-2015-0219 Django WSGI Header Spoofing Vulnerability pip · django, pip · Django 2015-01-16 medium5.3 CVE-2014-0483 Django data leakage via querystring manipulation in admin pip · Django 2014-08-26 medium6.5 CVE-2014-0482 Django Middleware Enables Session Hijacking pip · django, pip · Django 2014-08-26 medium6.1 CVE-2013-6044 Django cross-site scripting (XSS) vulnerability via is_safe_url function pip · Django 2013-10-04 medium6.1 CVE-2013-4249 Django cross-site scripting (XSS) vulnerability in the AdminURLFieldWidget widget pip · django 2013-10-04 medium5.3 CVE-2013-0306 Django is vulnerable to Denial of Service attack in formset pip · Django 2013-05-02 medium4.3 CVE-2013-0305 Django Data leakage via admin history log pip · Django 2013-05-02 medium4.0 CVE-2011-4136 Session manipulation in Django pip · Django 2011-10-19 medium6.1 CVE-2011-0697 Cross-site scripting in django pip · Django 2011-02-14 medium7.5 CVE-2010-4535 Improper date handling in Django pip · django, pip · Django 2011-01-10

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.