Skip to content
Noroxi
CVE-2014-3801· NVD / CVE Program· CNA mitre

OpenStack Orchestration API (Heat) 2013.2 through 2013.2.3 and 2014.1, when creating the stack for a template using a provider template, all

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 resource-type-list.

LowCVSS 3.5 · v2.0—No exploit Fix available
Published
May 23, 2014
Updated
Jun 16, 2026
EPSS
1.6% · 75th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

14

Monitor

Low priority for now.

CVSS
14 / 40 · 3.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.6%

Affected systems

VendorProduct
openstackheat

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openstack heat2013.2
  • openstack heat2013.2.1
  • openstack heat2013.2.2
  • openstack heat2013.2.3
  • openstack heat2014.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12heatbefore 2014.1-42014.1-4
PyPIopenstack-heatbefore 5.0.0a05.0.0a0
Red Hat:openstack:4::el6openstack-heatbefore 0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost
Red Hat:openstack:4::el6openstack-heat-apibefore 0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost
Red Hat:openstack:4::el6openstack-heat-api-cfnbefore 0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost
Red Hat:openstack:4::el6openstack-heat-api-cloudwatchbefore 0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost
Red Hat:openstack:4::el6openstack-heat-commonbefore 0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost
Red Hat:openstack:4::el6openstack-heat-enginebefore 0:2013.2.4-1.el6ost0:2013.2.4-1.el6ost

Other highest-scoring records for the same primary product.

  • CVE-2017-2621An 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 w
    22Monitor
  • CVE-2024-7319Openstack-heat: incomplete fix for cve-2023-1625
    20Monitor
  • CVE-2023-1625Information leak in api
    20Monitor
  • CVE-2016-9185In OpenStack Heat, by launching a new Heat stack with a local URL an authenticated user may conduct network discovery revealing internal net
    17Monitor
  • CVE-2013-6428The ReST API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 allows remote authenticated users t
    17Monitor
  • CVE-2013-6426The cloudformation-compatible API in OpenStack Orchestration API (Heat) before Havana 2013.2.1 and Icehouse before icehouse-2 does not prope
    16Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:heat2014.1-4 · Debian:12Package registry (OSV)
PyPI:openstack-heat5.0.0a0Package registry (OSV)
red hat:openstack-heat0:2013.2.4-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-heat-api0:2013.2.4-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-heat-api-cfn0:2013.2.4-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-heat-api-cloudwatch0:2013.2.4-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-heat-common0:2013.2.4-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)
red hat:openstack-heat-engine0:2013.2.4-1.el6ost · Red Hat:openstack:4::el6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

    If successful

    Confidentiality
    P · data can be read
    Integrity
    none
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    None
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:S/C:P/I:N/A:N

    nvd-primary

    Root cause

    The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    json
    {  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

    Fixed

    json
    {  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

    Noroxi analysis

    No Noroxi analysis for this record yet

    We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

    We use this product, ask for help

    Change log

    1. Fix✗ → ✓

    For records you follow, these changes also arrive as notifications. →

    References

    All records