NetSight

Security Dashboard

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

Reset
48 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.5 CVE-2014-3801 OpenStack Heat template URL information leakage pip · openstack-heat 2014-05-23 low3.1 CVE-2014-0134 OpenStack Nova host data leak to vm instance in rescue mode pip · nova 2014-05-08 low2.1 CVE-2013-4463 OpenStack Nova denial of service through compressed disk images pip · nova 2014-02-06 low3.3 CVE-2013-7048 OpenStack Nova live snapshots use an insecure local directory pip · nova 2014-01-23 low1.9 CVE-2013-6384 (1) impl_db2.py and (2) impl_mongodb.py in OpenStack Ceilometer 2013.2 and earlier, when the logging level is set to INFO, logs the connection string from ceil… openstack · ceilometer 2013-11-23 low2.1 CVE-2013-4354 The API before 2.1 in OpenStack Image Registry and Delivery Service (Glance) makes it easier for local users to inject images into arbitrary tenants by adding … openstack · image_registry_and_delivery_service_\(glance\) 2013-11-23 low3.3 CVE-2013-4477 OpenStack Identity Keystone Privilege Escalation vulnerability pip · keystone 2013-11-02 low1.9 CVE-2013-4469 OpenStack Compute (Nova) Denial of service due to improper validation of virtual size of QCOW2 image pip · nova 2013-11-02 low3.5 CVE-2013-4261 OpenStack Compute (Nova) Folsom, Grizzly, and earlier, when using Apache Qpid for the RPC backend, does not properly handle errors that occur during messaging,… openstack · folsom, openstack · grizzly, redhat · openstack 2013-10-29 low3.5 CVE-2013-4428 OpenStack Image Registry and Delivery Service (Glance) Folsom, Grizzly before 2013.1.4, and Havana before 2013.2, when the download_image policy is configured,… openstack · glance, canonical · ubuntu_linux 2013-10-27 low2.9 CVE-2013-2013 python-keystoneclient unsecure user password update pip · python-keystoneclient 2013-10-01 low3.5 CVE-2013-4278 OpenStack Compute (Nova) Resource limit circumvention in Nova private flavors pip · nova 2013-09-16 low2.1 CVE-2013-2006 OpenStack Keystone Sensitive information disclosure via log files pip · keystone 2013-05-21 low2.1 CVE-2013-1977 OpenStack devstack uses world-readable permissions for keystone.conf, which allows local users to obtain sensitive information such as the LDAP password and ad… openstack · devstack 2013-05-21 low2.1 CVE-2012-6120 Red Hat OpenStack Essex and Folsom creates the /var/log/puppet directory with world-readable permissions, which allows local users to obtain sensitive informat… redhat · openstack_essex, redhat · openstack_folsom 2013-04-10 low2.1 CVE-2012-5483 tools/sample_data.sh in OpenStack Keystone 2012.1.3, when access to Amazon Elastic Compute Cloud (Amazon EC2) is configured, uses world-readable permissions fo… openstack · keystone 2012-12-26 low3.5 CVE-2012-3371 OpenStack Nova Scheduler denial of service through scheduler_hints pip · Nova 2012-07-17 low3.5 CVE-2012-2101 Openstack Compute (Nova) Denial of service via network request that triggers large number of iptables rules pip · nova 2012-06-07

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.