NetSight

Security Dashboard

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

Reset
60 matching advisories · page 2 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 high8.1 CVE-2013-2228 SaltStack RSA Key Generation allows remote users to decrypt communications pip · salt 2019-12-03 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 medium5.3 CVE-2018-15750 SaltStack Salt Directory Traversal vulnerability in salt-api pip · salt 2018-10-24 high7.5 CVE-2018-1999027 An exposure of sensitive information vulnerability exists in Jenkins SaltStack Plugin 3.1.6 and earlier in SaltAPIBuilder.java, SaltAPIStep.java that allows at… maven · org.jenkins-ci.plugins:saltstack 2018-08-01 critical9.8 CVE-2017-7893 SaltStack Salt allows compromised salt-minions to impersonate the salt-master pip · salt 2018-04-23 high7.5 CVE-2017-14696 SaltStack Salt Denial of Service via a crafted authentication request pip · salt 2017-10-24 critical9.8 CVE-2017-14695 SaltStack Salt Directory traversal vulnerability in minion id validation pip · salt 2017-10-24 medium6.3 CVE-2015-6918 salt leaks git usernames and passwords to the log pip · salt 2017-10-10 high8.8 CVE-2017-5200 SaltStack Salt arbitrary command execution in Salt-api via ssh_client pip · salt 2017-09-26 high8.8 CVE-2017-5192 SaltStack Salt Authentication Bypass when using the local_batch client from salt-api pip · salt 2017-09-26 high7.5 CVE-2015-4017 Salt before 2014.7.6 does not verify certificates when connecting via the aliyun, proxmox, and splunk modules. pip · salt 2017-08-25 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 high7.8 CVE-2017-8109 SaltStack Salt Information Exposure pip · salt 2017-04-25 medium5.3 CVE-2015-1839 SaltStack has insecure /tmp file handling in salt/modules/chef.py pip · salt 2017-04-13 medium5.3 CVE-2015-1838 Salt improper handling of tmp files pip · salt 2017-04-13 critical9.1 CVE-2016-9639 Salt allows deleted minions to read or write to minions with the same id pip · salt 2017-02-07 medium5.6 CVE-2016-3176 Salt Insecure configuration of PAM external authentication service pip · salt 2017-01-31 low3.3 CVE-2015-8034 Salt uses weak permissions on the cache data pip · salt 2017-01-30 high8.1 CVE-2016-1866 Salt Improper Access Control pip · salt 2016-04-12 high7.2 CVE-2014-3563 SaltStack Salt Insecure Temporary File Creation pip · salt 2014-08-22 critical10.0 CVE-2013-6617 SaltStack Privilege Escalation vulnerability pip · salt 2013-11-05 high6.5 CVE-2013-4439 Minion identity not validated in saltstack pip · salt 2013-11-05 high7.5 CVE-2013-4438 Salt (aka SaltStack) before 0.17.1 allows remote attackers to execute arbitrary YAML code via unspecified vectors. saltstack · 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 high8.8 CVE-2013-4435 Salt has insufficient argument validation in several modules 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.