# CVE-2024-2905: Rpm-ostree: world-readable /etc/shadow file

> Attackers can read the world-readable /etc/shadow file in default rpm-ostree builds, exposing sensitive authentication data.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2024
- **Updated:** 6 Nov 2025
- **Also known as:** ALSA-2024:3823, AZL-42310, RHBA-2025:4872, RHSA-2024:3401, RHSA-2024:3823

## What is CVE-2024-2905?

CVE-2024-2905 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 25 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been discovered within rpm-ostree, pertaining to the /etc/shadow file in default builds having the world-readable bit enabled. This issue arises from the default permissions being set at a higher level than recommended, potentially exposing sensitive authentication data to unauthorized access.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2024-2905?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rpm-ostree` | AlmaLinux:9 | All versions | 2024.3-3.el9_4 |
| `rpm-ostree-libs` | AlmaLinux:9 | All versions | 2024.3-3.el9_4 |
| `rpm-ostree` | Red Hat:enterprise_linux:10.0 | All versions | 0:2025.5-1.el10 |
| `rpm-ostree-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:2025.5-1.el10 |
| `rpm-ostree-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:2025.5-1.el10 |
| `rpm-ostree-libs` | Red Hat:enterprise_linux:10.0 | All versions | 0:2025.5-1.el10 |
| `rpm-ostree-libs-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:2025.5-1.el10 |
| `rpm-ostree` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2024.3-3.el9_4 |
| `rpm-ostree-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2024.3-3.el9_4 |
| `rpm-ostree-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2024.3-3.el9_4 |
| `rpm-ostree-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2024.3-3.el9_4 |
| `rpm-ostree-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2024.3-3.el9_4 |
| `rpm-ostree` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2023.3-2.el9_2 |
| `rpm-ostree-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2023.3-2.el9_2 |
| `rpm-ostree-debugsource` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2023.3-2.el9_2 |
| `rpm-ostree-libs` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2023.3-2.el9_2 |
| `rpm-ostree-libs-debuginfo` | Red Hat:rhel_eus:9.2::appstream | All versions | 0:2023.3-2.el9_2 |

## How do I fix CVE-2024-2905?

Apply the vendor's patch.

## Is CVE-2024-2905 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2905 and fix it if it is affected.

What it is: CVE-2024-2905 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 25 Apr 2024. 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-2024-2905 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2024-2905/ (Markdown: https://insights.sbomify.com/CVE-2024-2905/index.md)
```

## Sources

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

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