Nova vulnerabilitiesRanked by how likely they are to be used.
Nova is made by Openstack. We track 38 published vulnerabilities in it, across 161 versions. None of them is on the list of flaws known to be exploited today. If you run Nova, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Nova vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Nova's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Nova flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 27%CVE-2021-3654Medium
A vulnerability was found in openstack-nova's console proxy, noVNC.
- 3.7%CVE-2017-18191High
An issue was discovered in OpenStack Nova 15.x through 15.1.0 and 16.x through 16.1.1.
- 3.7%CVE-2015-7713Medium
OpenStack Compute (Nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) do not properly apply security group changes, which allows remote attackers to bypass intended restriction by leveraging an instance...
- 3.5%CVE-2015-3241Medium
OpenStack Compute (nova) 2015.1 through 2015.1.1, 2014.2.3, and earlier does not stop the migration process when the instance is deleted, which allows remote authenticated users to cause a denial of service (disk,...
- 3.4%CVE-2015-3280Medium
OpenStack Compute (nova) before 2014.2.4 (juno) and 2015.1.x before 2015.1.2 (kilo) does not properly delete instances from compute nodes, which allows remote authenticated users to cause a denial of service (disk...
- 3.1%CVE-2015-5162High
The image parser in OpenStack Cinder 7.0.2 and 8.0.0 through 8.1.1; Glance before 11.0.1 and 12.0.0; and Nova before 12.0.4 and 13.0.0 does not properly limit qemu-img calls, which might allow attackers to cause a...
- 2.8%CVE-2014-3708Medium
OpenStack Compute (Nova) before 2014.1.4 and 2014.2.x before 2014.2.1 allows remote authenticated users to cause a denial of service (CPU consumption) via an IP filter in a list active servers API request.
- 2.3%CVE-2017-7214Critical
An issue was discovered in exception_wrapper.py in OpenStack Nova 13.x through 13.1.3, 14.x through 14.0.4, and 15.x through 15.0.1.
- 2.2%CVE-2015-8749Medium
The volume_utils._parse_volume_info function in OpenStack Compute (Nova) before 2015.1.3 (kilo) and 12.0.x before 12.0.1 (liberty) includes the connection_info dictionary in the StorageError message when using the...
- 2.1%CVE-2016-2140Medium
The libvirt driver in OpenStack Compute (Nova) before 2015.1.4 (kilo) and 12.0.x before 12.0.3 (liberty), when using raw storage and use_cow_images is set to false, allows remote authenticated users to read arbitrary...
Running Nova? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A vulnerability was found in openstack-nova's console proxy, noVNC. By crafting a malicious URL, noVNC could be made to redirect to any desired URL.
- Matched to
- Nova on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 38 published vulnerabilities listed under the name Nova, across 161 versions.
None of Nova's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Nova. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.