Heat vulnerabilitiesRanked by how likely they are to be used.
Heat is made by Openstack. We track 7 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Heat, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Heat vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Heat's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Heat 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.
- 1.7%CVE-2013-6428Medium
The ReST API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 allows remote authenticated users to bypass the tenant scoping restrictions via a modified tenant_id in the...
- 1.6%
OpenStack Orchestration API (Heat) 2013.2 through 2013.2.3 and 2014.1, when creating the stack for a template using a provider template, allows remote authenticated users to obtain the provider template URL via the...
- 1.5%CVE-2016-9185Medium
In OpenStack Heat, by launching a new Heat stack with a local URL an authenticated user may conduct network discovery revealing internal network configuration.
- 1.0%CVE-2013-6426Medium
The cloudformation-compatible API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 does not properly enforce policy rules, which allows local in-instance users to bypass...
- 0.7%CVE-2023-1625Medium
An information leak was discovered in OpenStack heat.
- 0.4%CVE-2017-2621Medium
An access-control flaw was found in the OpenStack Orchestration (heat) service before 8.0.0, 6.1.0 and 7.0.2 where a service log directory was improperly made world readable.
- 0.4%CVE-2024-7319Medium
An incomplete fix for CVE-2023-1625 was found in openstack-heat.
Running Heat? 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
The ReST API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 allows remote authenticated users to bypass the tenant scoping restrictions via a modified tenant_id in the request path.
- Matched to
- Heat 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 7 published vulnerabilities listed under the name Heat, across 12 versions.
None of Heat's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Heat. 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.