Skip to content
Fencer Intel
medium 4.0

CVE-2015-3010 json

ceph-deploy allows local users to obtain sensitive information by reading the file

published 2015-06-16 11 y ago modified 2026-06-17 4 mo ago also GHSA-9w4f-3v37-6f75 , PYSEC-2015-2 , EUVD-2015-0002

cvss
4.0
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 31%
public exploits
0
none known

Summary

ceph-deploy before 1.5.23 uses weak permissions (644) for ceph/ceph.client.admin.keyring, which allows local users to obtain sensitive information by reading the file.

Patch / fix

  • pypi ceph-deploy 1.5.23
  • ceph-deploy ceph storage 1.2 1.5.22-0.4.rc1.el6cp
  • ceph-deploy ceph storage 1.2 1.5.22-0.4.rc1.el7cp

red hat advisories RHSA-2015:1092

  • ceph Enterprise Storage 1.0 0.80.9-5.1
  • ceph-deploy Enterprise Storage 1.0 1.5.19+git.1431355031.6178cf3-9.1
  • python-Pillow Enterprise Storage 1.0 2.7.0-4.1
  • calamari-clients Enterprise Storage 1.0 1.2.2+git.1428648634.40dfe5b-3.1
  • python-djangorestframework Enterprise Storage 1.0 2.3.12-4.2

suse advisories SUSE-SU-2015:1102-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-2015-3010 updated cvss 4.9

ceph-deploy: keyring permissions are world readable in ~ceph

  • Red Hat Ceph Storage 1.1 ceph-deploy
    affected: no fix planned “Will not fix”
  • Red Hat Ceph Storage 1.2 for CentOS
    fixed: vendor fix RHSA-2015:1631
  • Red Hat Ceph Storage 1.2 for Ubuntu
    fixed: vendor fix RHSA-2015:1579
  • Red Hat Ceph Storage Installer 1.2 ceph-deploy 1.5.22-0.4.rc1.el6cp, ceph-deploy 1.5.22-0.4.rc1.el7cp
    fixed: vendor fix RHSA-2015:1092
  • Red Hat Ceph Storage 1.3 ceph-deploy
    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

0.38% chance of exploitation in the next 30 days, higher than 31% 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 4.0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi ceph-deploy
<1.5.23
1.5.23

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.