# CVE-2015-3010: ceph-deploy allows local users to obtain sensitive information by reading the file

> Local attackers can read sensitive Ceph admin keyring files due to weak file permissions in ceph-deploy.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9w4f-3v37-6f75, PYSEC-2015-2

## What is CVE-2015-3010?

CVE-2015-3010 is a low-severity vulnerability in n/a, published on 16 Jun 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-3010?

3 open source packages ship an affected version, including ceph-deploy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ceph-deploy` | PyPI | All versions | 1.5.23 |
| `ceph-deploy` | PyPI | All versions | 1.5.23 |
| `ceph-deploy` | PyPI | All versions | 1.5.23 |

Products: Ceph Ceph-Deploy.

## How do I fix CVE-2015-3010?

Upgrade ceph-deploy to 1.5.23 or later.

## Is CVE-2015-3010 being exploited?

There is no known exploitation of CVE-2015-3010 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-4053](https://insights.sbomify.com/CVE-2015-4053/): ceph-deploy uses world-readable permissions on client.admin key (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3010 and fix it if it is affected.

What it is: CVE-2015-3010 is a low-severity vulnerability in n/a, published on 16 Jun 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3010 in the wild and no public exploit code.

Affected packages and fixed versions:
- ceph-deploy (PyPI): affected all versions; fixed in 1.5.23
- ceph-deploy (PyPI): affected all versions; fixed in 1.5.23
- ceph-deploy (PyPI): affected all versions; fixed in 1.5.23

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-3010/ (Markdown: https://insights.sbomify.com/CVE-2015-3010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-3010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-3010
- OSV: https://osv.dev/vulnerability/CVE-2015-3010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-3010/
Summaries are generated and may contain mistakes; the official description above is the record.