NetSight

Security Dashboard

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

Reset
185 matching advisories · page 2 of 7Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2017-1000013 phpMyAdmin Open Redirect composer · phpmyadmin/phpmyadmin 2017-07-17 medium5.9 CVE-2016-9860 phpMyAdmin Denial of Service (DoS) composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.3 CVE-2016-9859 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-9858 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium6.1 CVE-2016-9857 phpMyAdmin XSS Vulnerability composer · phpmyadmin/phpmyadmin 2016-12-11 medium6.1 CVE-2016-9856 phpMyAdmin XSS Vulnerability composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.3 CVE-2016-9855 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-9854 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-9853 phpMyAdmin path disclosure composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.3 CVE-2016-9852 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-9851 phpMyAdmin Bypass logout timeout composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.3 CVE-2016-9850 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-9848 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-9847 phpMyAdmin Cryptographic Vulnerability composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.9 CVE-2016-6632 phpMyAdmin Denial of service (DOS) attack with dbase extension composer · phpmyadmin/phpmyadmin 2016-12-11 medium6.5 CVE-2016-6630 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium6.3 CVE-2016-6628 phpMyAdmin Reflected File Download attack composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.3 CVE-2016-6627 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium5.4 CVE-2016-6626 An issue was discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium4.3 CVE-2016-6625 phpMyAdmin allows to detect if user is logged in composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.9 CVE-2016-6624 phpMyAdmin IPv6 and proxy server IP-based authentication rule circumvention composer · phpmyadmin/phpmyadmin 2016-12-11 medium6.5 CVE-2016-6623 phpMyAdmin DoS Vulnerability composer · phpmyadmin/phpmyadmin 2016-12-11 medium5.9 CVE-2016-6622 phpMyAdmin DoS Vulnerability composer · phpmyadmin/phpmyadmin 2016-12-11 medium6.5 CVE-2016-6618 phpMyAdmin Denial of service (DOS) attack in transformation feature composer · phpmyadmin/phpmyadmin 2016-12-11 medium6.1 CVE-2016-6615 XSS issues were discovered in phpMyAdmin. phpmyadmin · phpmyadmin 2016-12-11 medium6.8 CVE-2016-6614 An issue was discovered in phpMyAdmin involving the %u username replacement functionality of the SaveDir and UploadDir features. phpmyadmin · phpmyadmin 2016-12-11 medium5.3 CVE-2016-6613 phpMyAdmin Local file exposure through symlinks with UploadDir composer · phpmyadmin/phpmyadmin 2016-12-11 medium6.5 CVE-2016-6612 phpMyAdmin Local file exposure composer · phpmyadmin/phpmyadmin 2016-12-11 medium4.3 CVE-2016-6610 A full path disclosure vulnerability was discovered in phpMyAdmin where a user can trigger a particular error in the export mechanism to discover the full path… phpmyadmin · phpmyadmin 2016-12-11 medium6.1 CVE-2016-6608 phpMyAdmin Cross-site Scripting (XSS) composer · phpmyadmin/phpmyadmin 2016-12-11

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.