Skip to content
Fencer Intel
medium 6.2

CVE-2013-4183 json

OpenStack Cinder LVMVolumeDriver does not zero deleted snapshots

published 2013-09-16 13 y ago modified 2026-06-16 4 mo ago also GHSA-q3rw-wcj6-8cjf , PYSEC-2013-35 , EUVD-2013-0003

cvss
6.2
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

The clear_volume function in LVMVolumeDriver driver in OpenStack Cinder 2013.1.1 through 2013.1.2 does not properly clear data when deleting a snapshot, which allows local users to obtain sensitive information via unspecified vectors.

Patch / fix

  • pypi cinder 7.0.0a0
  • cinder Debian 14, Debian 13, Debian 12 2013.1.2-4

debian advisories DEBIAN-CVE-2013-4183

  • openstack-cinder openstack 3 2013.1.3-2.el6ost
  • python-cinder openstack 3 2013.1.3-2.el6ost

red hat advisories RHSA-2013:1198

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-2013-4183 updated cvss 3.5

OpenStack: Cinder LVM volume driver does not support secure deletion

  • Red Hat OpenStack Platform 4 openstack-cinder
    affected: no fix available
  • Red Hat Enterprise Linux OpenStack Platform 3.0 python-cinder 2013.1.3-2.el6ost, openstack-cinder 2013.1.3-2.el6ost
    fixed: vendor fix RHSA-2013:1198

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.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi cinder
<7.0.0a0
7.0.0a0

Classification

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

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.