Skip to content
Fencer Intel
medium 5.5

CVE-2015-8234 json

OpenStack Glance Signature Verification Bypass

published 9y ago modified 4mo ago also GHSA-wmhw-fvg9-87fc , PYSEC-2017-143 , EUVD-2017-0145

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

Summary

The image signature algorithm in OpenStack Glance 11.0.0 allows remote attackers to bypass the signature verification process via a crafted image, which triggers an MD5 collision.

Patch / fix

Is CVE-2015-8234 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2015-8234 updated cvss 2.4

openstack-glance: MD5 used for cryptographic signature verification

  • Red Hat OpenStack Platform 8 (Liberty) python-glance, openstack-glance
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) python-glance, openstack-glance, python-glance-tests Red Hat OpenStack Platform 16.2 python3-glance, openstack-glance Red Hat OpenStack Platform 17.1 python3-glance, openstack-glance
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 18.0 openstack-glance
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) openstack-glance Red Hat Enterprise Linux OpenStack Platform 6 (Juno) openstack-glance Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) python-glance, openstack-glance
    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.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi glance
<=11.0.0
 no fix listed

Classification

Weakness

References

Sources

Fencer Intel 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.