Skip to content
Fencer Intel
medium 4.7

CVE-2015-2687 json

OpenStack Compute (Nova) Improper Access Control

published 2017-08-09 9 y ago modified 2026-06-17 4 mo ago also GHSA-97fv-22hc-mrgj , PYSEC-2017-145 , EUVD-2017-0079

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

Summary

OpenStack Compute (nova) Icehouse, Juno and Havana when live migration fails allows local users to access VM volumes that they would normally not have permissions for.

Patch / fix

  • pypi nova 15.0.0.0b1
  • nova Debian 14, Debian 13, Debian 12 2014.1-1

debian advisories DEBIAN-CVE-2015-2687

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-2687 updated cvss 1.0

openstack-nova: information leak when live-migration failed

  • Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) openstack-nova Red Hat Enterprise Linux OpenStack Platform 6 (Juno) openstack-nova
    affected: no fix available “Fix deferred”
  • Red Hat OpenStack Platform 4 openstack-nova
    affected: no fix planned “Will not fix”

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

0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
pypi nova
<15.0.0.0b1
15.0.0.0b1

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.