NetSight

Security Dashboard

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

Reset
24 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.6 CVE-2024-38824 Salt vulnerable to directory traversal attack in file receiving method pip · salt 2025-06-13 critical9.8 CVE-2021-33226 Buffer Overflow vulnerability in Saltstack v.3003 and before allows attacker to execute arbitrary code via the func variable in salt/salt/modules/status.py fil… saltstack · salt 2023-02-17 critical GHSA-q427-wgh7-m7q7 Malware in @saltstack/fetlife-assetsMalware npm · @saltstack/fetlife-assets 2022-06-20 critical9.8 CVE-2021-25315 CWE - CWE-287: Improper Authentication vulnerability in SUSE Linux Enterprise Server 15 SP 3; openSUSE Tumbleweed allows local attackers to execute arbitrary c… pip · salt 2021-03-03 critical9.8 CVE-2021-3197 SaltStack Salt is vulnerable to shell injection via ProxyCommand argument pip · salt 2021-02-27 critical9.8 CVE-2021-3148 SaltStack Salt command injection in the Salt-API when using the Salt-SSH client pip · salt 2021-02-27 critical9.1 CVE-2021-3144 SaltStack Salt eauth tokens can be used once after expiration pip · salt 2021-02-27 critical9.8 CVE-2021-25283 SaltStack Salt Server Side Template Injection pip · salt 2021-02-27 critical9.1 CVE-2021-25282 SaltStack Salt Directory Traversal vulnerability pip · salt 2021-02-27 critical9.8 CVE-2021-25281 SaltStack Salt Improper Authentication vulnerability pip · salt 2021-02-27 critical9.8 CVE-2020-25592 SaltStack Salt Improper Validation of eauth credentials and tokens in salt-netapi pip · salt 2020-11-06 critical9.8 CVE-2020-16846 SaltStack Salt Command Injection in netapi ssh clientExploited pip · salt 2020-11-06 critical9.8 CVE-2020-11651 SaltStack Salt Unauthenticated Remote Code ExecutionExploited pip · salt 2020-04-30 critical9.8 CVE-2019-17361 SaltStack Salt is vulnerable to command injection pip · salt 2020-01-17 critical9.8 CVE-2019-1010259 SaltStack Salt SQL Injection vulnerability in mysql.user_chpass function pip · salt 2019-07-18 critical9.8 CVE-2018-15751 SaltStack Salt Remote command execution and incorrect access control when using salt-api pip · salt 2018-10-24 critical9.8 CVE-2017-7893 SaltStack Salt allows compromised salt-minions to impersonate the salt-master pip · salt 2018-04-23 critical9.8 CVE-2017-14695 SaltStack Salt Directory traversal vulnerability in minion id validation pip · salt 2017-10-24 critical9.8 CVE-2017-12791 SaltStack Salt Directory traversal vulnerability in minion id validation pip · salt 2017-08-23 critical9.8 CVE-2015-6941 salt password information leaked in debug logs pip · salt 2017-08-09 critical9.1 CVE-2016-9639 Salt allows deleted minions to read or write to minions with the same id pip · salt 2017-02-07 critical10.0 CVE-2013-6617 SaltStack Privilege Escalation vulnerability pip · salt 2013-11-05 critical10.0 CVE-2013-4437 SaltStack insecurely uses /tmp pip · salt 2013-11-05 critical9.3 CVE-2013-4436 SaltStack MITM SSH attack in salt-ssh pip · salt 2013-11-05

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.