NetSight

Security Dashboard

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

Reset
634 matching advisories · page 21 of 22Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.0 CVE-2013-1664 XML Entity Expansion (XEE) in Django pip · Django 2013-04-03 medium5.3 CVE-2013-1865 OpenStack Keystone Improper Authentication vulnerability pip · keystone 2013-03-22 medium6.5 CVE-2013-1840 OpenStack Glance is vulnerable to Exposure of Sensitive Information pip · glance 2013-03-22 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 medium5.5 CVE-2013-0266 A flaw was found in the `puppetlabs-cinder` module, as used in PackStack. openstack · essex, openstack · folsom 2013-03-08 high8.8 CVE-2013-0261 A flaw was found in PackStack. openstack · essex, openstack · folsom 2013-03-08 medium4.0 CVE-2013-0212 OpenStack Glance logs user name and password in cleartext pip · glance 2013-02-24 medium5.0 CVE-2013-0247 OpenStack Keystone Essex 2012.1.3 and earlier, Folsom 2012.2.3 and earlier, and Grizzly grizzly-2 and earlier allows remote attackers to cause a denial of serv… openstack · keystone, canonical · ubuntu_linux 2013-02-24 medium6.5 CVE-2013-0208 The boot-from-volume feature in OpenStack Compute (Nova) Folsom and Essex, when using nova-volumes, allows remote authenticated users to boot from other users'… openstack · essex, openstack · folsom, canonical · ubuntu_linux 2013-02-13 medium6.5 CVE-2012-5625 OpenStack Nova Information leak in libvirt LVM-backed instances pip · nova 2012-12-26 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 medium5.4 CVE-2012-5571 OpenStack Keystone intended authorization restrictions bypass pip · Keystone 2012-12-18 high5.9 CVE-2012-5563 OpenStack Keystone Insufficient token expiration pip · keystone 2012-12-18 medium5.5 CVE-2012-5482 OpenStack Glance arbitrary deletion of non-protected images pip · glance 2012-11-11 medium5.5 CVE-2012-4573 OpenStack Glance arbitrary deletion of non-protected images pip · glance 2012-11-11 critical9.8 CVE-2012-4406 OpenStack Object Storage (swift) Code Injection vulnerability pip · swift 2012-10-22 medium4.0 CVE-2012-4457 OpenStack Keystone Token authorization for a user in a disabled tenant is allowed pip · Keystone 2012-10-09 high7.5 CVE-2012-4456 OpenStack Keystone Improper Authentication vulnerability pip · keystone 2012-10-09 medium4.0 CVE-2012-4413 OpenStack Keystone does not invalidate existing tokens when granting or revoking roles pip · keystone 2012-09-18 high7.5 CVE-2012-3542 OpenStack Keystone Allows Remote User Account Creation pip · keystone 2012-09-05 medium5.8 CVE-2012-3540 Open redirect vulnerability in views/auth_forms.py in OpenStack Dashboard (Horizon) Essex (2012.1) allows remote attackers to redirect users to arbitrary web s… openstack · horizon 2012-09-05 high6.5 CVE-2012-3447 Arbitrary file overwrite in OpenStack Nova pip · nova 2012-08-20 medium4.0 CVE-2012-1585 OpenStack Nova Long server names grow nova-api log files significantly pip · nova 2012-08-17 medium4.9 CVE-2012-3426 OpenStack Keystone token expiration issues pip · Keystone 2012-07-31 medium5.5 CVE-2012-3361 OpenStack Nova Arbitrary file injection/corruption through directory traversal issues pip · nova 2012-07-22 medium5.5 CVE-2012-3360 OpenStack Nova Directory traversal vulnerability pip · nova 2012-07-22 low3.5 CVE-2012-3371 OpenStack Nova Scheduler denial of service through scheduler_hints pip · Nova 2012-07-17 medium4.3 CVE-2012-2654 OpenStack Compute (Nova) Improper Input Validation pip · nova 2012-06-21 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.