NetSight

Security Dashboard

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

Reset
211 matching advisories · page 7 of 8Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high6.5 CVE-2015-5163 OpenStack Image Service (Glance) allows remote authenticated users to read arbitrary file pip · glance 2015-08-19 high7.5 CVE-2015-3209 Heap-based buffer overflow in the PCNET controller in QEMU allows remote attackers to execute arbitrary code by sending a packet with TXSTATUS_STARTPACKET set … qemu · qemu, juniper · junos_space, canonical · ubuntu_linux +9 2015-06-15 high7.7 CVE-2015-3456 The Floppy Disk Controller (FDC) in QEMU, as used in Xen 4.5.x and earlier and KVM, allows local guest users to cause a denial of service (out-of-bounds write … qemu · qemu, redhat · enterprise_virtualization, redhat · openstack +2 2015-05-13 high7.5 CVE-2015-1852 OpenStack keystonemiddleware and python-keystoneclient vulnerable to man-in-the-middle attacks pip · keystonemiddleware, pip · python-keystoneclient 2015-04-17 high7.5 CVE-2014-3691 Smart Proxy (aka Smart-Proxy and foreman-proxy) in Foreman before 1.5.4 and 1.6.x before 1.6.2 does not validate SSL certificates, which allows remote attacker… redhat · openstack, theforeman · foreman 2015-03-09 high7.5 CVE-2015-1881 OpenStack Glance Denial of service by creating a large number of images pip · glance 2015-02-24 high6.5 CVE-2014-9684 OpenStack Glance Denial of service by creating a large number of images pip · glance 2015-02-24 high7.6 CVE-2014-3632 The default configuration in a sudoers file in the Red Hat openstack-neutron package before 2014.1.2-4, as used in Red Hat Enterprise Linux Open Stack Platform… openstack · neutron 2014-10-07 high5.9 CVE-2014-7144 OpenStack keystonemiddleware does not verify certificate pip · keystonemiddleware, pip · python-keystoneclient 2014-10-02 high6.5 CVE-2014-5253 OpenStack Keystone Domain-scoped tokens don't get revoked pip · keystone 2014-08-25 high6.5 CVE-2014-5252 OpenStack Identity (Keystone) UUID v2 tokens does not expire with revocation events pip · keystone 2014-08-25 high6.5 CVE-2014-5251 OpenStack Identity (Keystone) Multiple vulnerabilities in revocation events pip · keystone 2014-08-25 high7.6 CVE-2013-6433 The default configuration in the Red Hat openstack-neutron package before 2013.2.3-7 does not properly set a configuration file for rootwrap, which allows remo… openstack · neutron, canonical · ubuntu_linux 2014-06-02 high7.5 CVE-2014-2828 OpenStack Identity (Keystone) DoS through V3 API authentication chaining pip · keystone 2014-04-15 high6.5 CVE-2014-2237 OpenStack Identity (Keystone) Trustee token revocations does not work with memcache backend pip · keystone 2014-04-01 high6.5 CVE-2014-2573 The VMWare driver in OpenStack Compute (Nova) 2013.2 through 2013.2.2 does not properly put VMs into RESCUE status, which allows remote authenticated users to … pip · nova 2014-03-25 high7.5 CVE-2013-7130 OpenStack Nova Live migration can leak root disk into ephemeral storage pip · nova 2014-02-06 high7.5 CVE-2014-0006 OpenStack Swift Discloses Secret URLs to Timing Attack pip · swift 2014-01-23 high7.5 CVE-2013-2104 python-keystoneclient missing expiration check in PKI token validation pip · python-keystoneclient 2014-01-21 high7.5 CVE-2013-4386 Multiple SQL injection vulnerabilities in app/models/concerns/host_common.rb in Foreman before 1.2.3 allow remote attackers to execute arbitrary SQL commands v… redhat · openstack, theforeman · foreman 2013-11-20 high7.5 CVE-2013-4182 app/controllers/api/v1/hosts_controller.rb in Foreman before 1.2.2 does not properly restrict access to hosts, which allows remote attackers to access arbitrar… redhat · openstack, theforeman · foreman 2013-09-16 high7.5 CVE-2013-4111 python-glanceclient vulnerable to SSL server spoofing due to unverified X.509 certificate pip · python-glanceclient 2013-08-28 high7.5 CVE-2013-2161 OpenStack Swift Unchecked user input in XML responses pip · swift 2013-08-20 high7.5 CVE-2013-2882 Google V8, as used in Google Chrome before 28.0.1500.95, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vec… google · chrome, redhat · openstack, debian · debian_linux +1 2013-07-31 high6.5 CVE-2013-1838 OpenStack Compute (Nova) Denial of service via a large number of calls to the addFixedIp function pip · nova 2013-03-22 high6.5 CVE-2013-0335 OpenStack Compute Nova Unauthorised access to arbitrary VM using VNC token from deleted VM pip · Nova 2013-03-22 high8.8 CVE-2013-0261 A flaw was found in PackStack. openstack · essex, openstack · folsom 2013-03-08 high5.9 CVE-2012-5563 OpenStack Keystone Insufficient token expiration pip · keystone 2012-12-18 high7.5 CVE-2012-4456 OpenStack Keystone Improper Authentication vulnerability pip · keystone 2012-10-09 high7.5 CVE-2012-3542 OpenStack Keystone Allows Remote User Account Creation pip · keystone 2012-09-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.