# CVE-2024-22037: Database password leaked by systemd uyuni-server-attestation service

> Local attackers can read the database password from the systemd environment of the uyuni-server-attestation service, compromising database security.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **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:** 28 Nov 2024
- **Updated:** 28 Nov 2024
- **Also known as:** GHSA-4mrg-r3f5-vhvf, SUSE-EL-9-CLIENT-TOOLS-2025-532, SUSE-RU-2024:4008-1, SUSE-SU-2025:0532-1, SUSE-SU-2025:20124-1

## What is CVE-2024-22037?

CVE-2024-22037 is a medium-severity vulnerability in SUSE Manager Server 5.0, published on 28 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The uyuni-server-attestation systemd service needs a database_password environment variable. This file has 640 permission, and cannot be shown users, but the environment is still exposed by systemd to non-privileged users.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `scap-security-guide` | SUSE:EL-9:Update:Products:ManagerTools:Update | All versions | 0.1.75-1.32.1 |
| `spacecmd` | SUSE:EL-9:Update:Products:ManagerTools:Update | All versions | 5.0.11-1.44.1 |
| `uyuni-tools` | SUSE:EL-9:Update:Products:ManagerTools:Update | All versions | 0.1.28-1.14.1 |
| `salt` | SUSE:Linux Micro 6.0 | All versions | 3006.0-9.1 |
| `scap-security-guide` | SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | All versions | 0.1.75-1.32.1 |
| `scap-security-guide` | SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | All versions | 0.1.75-1.32.1 |
| `spacecmd` | SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | All versions | 5.0.11-1.44.1 |
| `spacecmd` | SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | All versions | 5.0.11-1.44.1 |
| `uyuni-tools` | SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | All versions | 0.1.28-1.14.1 |
| `uyuni-tools` | SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | All versions | 0.1.28-1.14.1 |
| `uyuni-storage-setup` | SUSE:Manager Proxy 5.0 | All versions | 5.0.3-150500.12.6.4 |
| `uyuni-tools` | SUSE:Manager Proxy 5.0 | All versions | 0.1.26-150500.3.12.2 |
| `uyuni-storage-setup` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 5.0.3-150500.12.6.4 |
| `uyuni-tools` | SUSE:Manager Retail Branch Server Extension 5.0 | All versions | 0.1.26-150500.3.12.2 |
| `uyuni-storage-setup` | SUSE:Manager Server 5.0 | All versions | 5.0.3-150500.12.6.4 |
| `uyuni-tools` | SUSE:Manager Server 5.0 | All versions | 0.1.26-150500.3.12.2 |

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

Apply the vendor's patch.

## Is CVE-2024-22037 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22037 is a medium-severity vulnerability in SUSE Manager Server 5.0, published on 28 Nov 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-22037 in the wild and no public exploit code.

Affected product: SUSE Manager Server 5.0. 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-22037/ (Markdown: https://insights.sbomify.com/CVE-2024-22037/index.md)
```

## Sources

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

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