How severe is CVE-2015-4053?

No CVSS score has been assigned to CVE-2015-4053 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-4053?

CVE-2015-4053 affects the following packages: ceph-deploy (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2015-4053?

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

How do I detect CVE-2015-4053 in my PyPI dependencies?

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.

How do I mitigate CVE-2015-4053 if there is no patch (or I can't update yet)?

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.

Is CVE-2015-4053 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-4053 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-4053?

CVE-2015-4053 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2015-4053?

CVE-2015-4053 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2015-4053 published, and has it been updated?

CVE-2015-4053 was published on May 17, 2022 and was last updated on December 8, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2015-4053 — ceph-deploy

Fix: ceph/ceph-deploy#300

CVE-2015-4053 is a Information Exposure vulnerability in ceph-deploy. A fix is available for ceph-deploy — see the affected versions and patch details below.

ceph-deploy uses world-readable permissions on client.admin key

Also known asPYSEC-2015-3

Published

May 17, 2022

Updated

Dec 8, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 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 CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

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

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

The admin command in ceph-deploy before 1.5.25 uses world-readable permissions for /etc/ceph/ceph.client.admin.keyring, which allows local users to obtain sensitive information by reading the file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ceph-deploy`	all versions	1.5.25`pip install --upgrade 'ceph-deploy==1.5.25'`

Affected Products

1 product · 1 configurations

Application

ceph-deployceph

≤ 1.5.22

range

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update ceph-deploy to 1.5.25 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-4053 is resolved across your whole dependency graph.
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

Product	Fixed in	Advisory
Red Hat Ceph Storage 1.2 for CentOS	see advisory	RHSA-2015:1631
Red Hat Ceph Storage 1.2 for RHEL 6	`ceph-deploy-0:1.5.22-0.4.rc1.el6cp`	RHSA-2015:1092
Red Hat Ceph Storage 1.2 for Ubuntu	see advisory	RHSA-2015:1579

Frequently Asked Questions

The admin command in ceph-deploy before 1.5.25 uses world-readable permissions for `/etc/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-4053 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works