Skip to content
Fencer Vulns
critical 9.8

CVE-2016-7404 json

Openstack Magnum Unsafe Credential Handling

published 2019-06-21 7 y ago modified 2026-07-01 4 mo ago also GHSA-793v-r35j-9rp9 , PYSEC-2026-437 , EUVD-2022-2957

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

OpenStack Magnum passes OpenStack credentials into the Heat templates creating its instances. While these should just be used for retrieving the instances' SSL certificates, they allow full API access, though and can be used to perform any API operation the user is authorized to perform.

Patch / fix

  • pypi openstack-magnum 5.0.0
  • magnum Debian 14, Debian 13, Debian 12 3.1.1-5

debian advisories DEBIAN-CVE-2016-7404

  • openstack-magnum OpenStack Cloud 7 3.1.2~a0~dev20-9.4

suse advisories SUSE-SU-2017:1233-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-7404 updated cvss 8.5

openstack-magnum: Magnum created instances have full API access to creating user's OpenStack account

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.88% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi openstack-magnum
<5.0.0
5.0.0

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.