NetSight

Security Dashboard

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

Reset
211 matching advisories · page 4 of 8Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.3 CVE-2019-10141 Openstack ironic-inspector has SQL injection vulnerability in node_cache pip · ironic-inspector 2019-07-30 high7.2 CVE-2019-10193 A stack-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before 3.2.13, 4.x before 4.0.14 and 5.x before 5.0.4. redislabs · redis, redhat · openstack, redhat · enterprise_linux +6 2019-07-11 high7.2 CVE-2019-10192 A heap-buffer overflow vulnerability was found in the Redis hyperloglog data structure versions 3.x before 3.2.13, 4.x before 4.0.14 and 5.x before 5.0.4. redislabs · redis, redhat · openstack, redhat · software_collections +7 2019-07-11 high8.0 CVE-2019-3895 Openstack Octavia Access Control Vulnerability pip · octavia 2019-06-03 high7.4 CVE-2019-0223 While investigating bug PROTON-2014, we discovered that under some circumstances Apache Qpid Proton versions 0.9 to 0.27.0 (C library and its language bindings… maven · org.apache.qpid:proton-j 2019-04-23 high8.6 CVE-2011-3147 Openstack nova qcow format could expose host filesystem information pip · nova 2019-04-22 high6.5 CVE-2019-10876 OpenStack Neutron overlapping security group rules prevents compute node network configuration pip · neutron 2019-04-05 high7.8 CVE-2019-3830 Ceilometer Prints Sensitive Configuration Data to Log pip · ceilometer 2019-03-26 high7.5 CVE-2018-16856 Openstack Octavia allows Insertion of Sensitive Information into Log File pip · octavia 2019-03-26 high6.5 CVE-2019-9735 OpenStack Neutron's unsupported dport option prevents applying security groups pip · neutron 2019-03-13 high5.3 CVE-2018-16876 Ansible sensitive information disclosure pip · ansible 2019-01-03 high7.5 CVE-2018-12122 Node.js: All versions prior to Node.js 6.15.0, 8.14.0, 10.14.0 and 11.3.0: Slowloris HTTP Denial of Service: An attacker can cause a Denial of Service (DoS) by… nodejs · node.js, suse · suse_enterprise_storage, suse · suse_linux_enterprise_server +1 2018-11-28 high7.5 CVE-2018-12116 Node.js: All versions prior to Node.js 6.15.0 and 8.14.0: HTTP request splitting: If Node.js can be convinced to use unsanitized user-provided Unicode data for… nodejs · node.js, suse · suse_enterprise_storage, suse · suse_linux_enterprise_server +1 2018-11-28 high7.5 CVE-2018-7977 There is an information leakage vulnerability on several Huawei products. huawei · fusionsphere_openstack 2018-11-27 high7.5 CVE-2018-16849 openstack-mistral Discloses the presence of arbitrary files within the filesystem pip · mistral 2018-11-02 high5.9 CVE-2018-1000808 Pyopenssl Incorrect Memory Management pip · pyopenssl 2018-10-08 high8.1 CVE-2018-1000807 PyOpenSSL Use-After-Free vulnerability pip · pyopenssl 2018-10-08 high7.5 CVE-2018-17205 An issue was discovered in Open vSwitch (OvS) 2.7.x through 2.7.6, affecting ofproto_rule_insert__ in ofproto/ofproto.c. openvswitch · openvswitch, redhat · openstack, canonical · ubuntu_linux 2018-09-19 high6.5 CVE-2018-14635 OpensStack Neutron Denial of Service Vulnerability pip · neutron 2018-09-10 high7.5 CVE-2017-15139 A vulnerability was found in openstack-cinder releases up to and including Queens, allowing newly created volumes in certain storage volume configurations to c… openstack · cinder, redhat · openstack 2018-08-27 high8.2 CVE-2017-2627 A flaw was found in openstack-tripleo-common as shipped with Red Hat Openstack Enterprise 10 and 11. redhat · openstack, openstack · tripleo-common 2018-08-22 high8.5 CVE-2018-10915 A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. redhat · openstack, redhat · virtualization, redhat · enterprise_linux_desktop +6 2018-08-09 high8.8 CVE-2018-10898 A vulnerability was found in openstack-tripleo-heat-templates before version 8.0.2-40. redhat · openstack, openstack · tripleo_heat_templates 2018-07-30 high7.5 CVE-2018-10903 A flaw was found in python-cryptography versions between >=1.9.0 and <2.3. pip · cryptography 2018-07-30 high7.2 CVE-2017-2673 OpenStack Identity service (keystone) Incorrect Authorization pip · keystone 2018-07-19 high7.8 CVE-2018-10875 Ansible Arbitrary Code Execution pip · ansible 2018-07-13 high5.9 CVE-2018-10855 Ansible exposes sensitive data in log files and on the terminal pip · ansible 2018-07-03 high7.8 CVE-2018-10874 Ansible Improper Input Validation vulnerability pip · ansible 2018-07-02 high8.8 CVE-2018-1000603 A exposure of sensitive information vulnerability exists in Jenkins Openstack Cloud Plugin 2.35 and earlier in BootSource.java, InstancesToRun.java, JCloudsCle… maven · org.jenkins-ci.plugins:openstack-cloud 2018-06-26 high8.0 CVE-2017-7466 Ansible Arbitrary Code Execution pip · ansible 2018-06-22

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.