NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2015-3010 — ceph-deploy

MEDIUMFix: ceph/ceph-deploy#272

CVE-2015-3010 is a medium-severity (CVSS 4) Information Exposure vulnerability in ceph-deploy. A fix is available for ceph-deploy — see the affected versions and patch details below.

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

Also known asPYSEC-2015-2
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk
0.00%0.29%0.59%0.88%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍ceph-deploy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIceph-deployall versions1.5.23pip install --upgrade 'ceph-deploy==1.5.23'

Affected Products

1 product · 1 configurations
Application
ceph-deployceph
1 version
1.5.22

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ceph-deploy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ceph-deploy to 1.5.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-3010 is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat Ceph Storage 1.2 for CentOSsee advisoryRHSA-2015:1631
Red Hat Ceph Storage 1.2 for RHEL 6ceph-deploy-0:1.5.22-0.4.rc1.el6cpRHSA-2015:1092
Red Hat Ceph Storage 1.2 for Ubuntusee advisoryRHSA-2015:1579

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2015-3010 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2015-3010: ceph-deploy — Fixed in 1.5.23