NetSight

Security Dashboard

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

Reset
55 matching advisories · page 2 of 2Index updated 5 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2024-49754 LibreNMS has a stored XSS ('Cross-site Scripting') in librenms/includes/html/pages/api-access.inc.php composer · librenms/librenms 2024-11-15 high7.5 CVE-2024-47523 LibreNMS has Stored Cross-site Scripting vulnerability in "Alert Transports" feature composer · librenms/librenms 2024-10-01 high7.2 CVE-2024-47524 LibreNMS has Stored Cross-site Scripting vulnerability in "Device Group" Name composer · librenms/librenms 2024-10-01 high7.5 CVE-2024-47525 LibreNMS has Stored Cross-site Scripting vulnerability in "Alert Rules" feature composer · librenms/librenms 2024-10-01 high7.5 CVE-2024-47527 LibreNMS has Stored Cross-site Scripting vulnerability in "Device Dependencies" feature composer · librenms/librenms 2024-10-01 high7.2 CVE-2024-32480 LibreNMS vulnerable to a Time-Based Blind SQL injection leads to database extraction composer · librenms/librenms 2024-04-22 high7.1 CVE-2024-32479 LibreNMS uses Improper Sanitization on Service template name leads to Stored XSS composer · librenms/librenms 2024-04-22 high8.8 CVE-2024-32461 LibreNMS vulnerable to SQL injection time-based leads to database extraction composer · librenms/librenms 2024-04-22 high7.8 CVE-2023-5591 SQL injection in librenms/librenms composer · librenms/librenms 2023-10-16 high8.4 CVE-2023-5060 Cross site scripting in librenms composer · librenms/librenms 2023-09-19 high7.6 CVE-2023-4347 LibreNMS Cross-site Scripting vulnerability composer · librenms/librenms 2023-08-15 high7.6 CVE-2022-4068 Cross-site Scripting in librenms/librenms composer · librenms/librenms 2022-11-20 high8.8 CVE-2022-3525 Deserialization of Untrusted Data in librenms/librenms composer · librenms/librenms 2022-11-20 high7.1 CVE-2022-0588 Missing Authorization in librenms/librenms composer · librenms/librenms 2022-02-15 high7.1 CVE-2022-0587 Improper Authorization in librenms composer · librenms/librenms 2022-02-15 high7.1 CVE-2022-0580 Improper Access Control in librenms composer · librenms/librenms 2022-02-14 high8.8 CVE-2020-35700 SQL Injection in librenms composer · librenms/librenms 2021-02-08 high8.8 CVE-2020-15877 Exposure of Resource to Wrong Sphere in LibreNMS composer · librenms/librenms 2020-07-21 high8.1 CVE-2019-12465 SQL Injection in LibreNMS composer · librenms/librenms 2019-09-09 high7.5 CVE-2019-12464 Path Traversal in LibreNMS composer · librenms/librenms 2019-09-09 high8.8 CVE-2019-12463 Improper Encoding or Escaping of Output and Injection in LibreNMS composer · librenms/librenms 2019-09-09 high8.8 CVE-2019-10671 SQL Injection in LibreNMS composer · librenms/librenms 2019-09-09 high7.2 CVE-2019-10669 An issue was discovered in LibreNMS through 1.47. librenms · librenms 2019-09-09 high8.1 CVE-2019-10666 An issue was discovered in LibreNMS through 1.47. librenms · librenms 2019-09-09 high8.8 CVE-2018-20678 LibreNMS SQL Injection composer · librenms/librenms 2019-03-28

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.