# CVE-2024-52869: Privilege escalation in n/a

> Incorrect group assignments during SLES OS migration allow service accounts to gain higher privileges, potentially leading to full system compromise.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2025
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-w6w8-xwp9-3vwq

## What is CVE-2024-52869?

CVE-2024-52869 is a medium-severity vulnerability in n/a, published on 8 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Certain Teradata account-handling code through 2024-11-04, used with SUSE Enterprise Linux Server, mismanages groups. Specifically, when there is an operating system move from SUSE Enterprise Linux Server (SLES) 12 Service Pack (SP) 2 or 3 to SLES 15 SP2 on Teradata Database systems, some service/system user accounts, and possibly systems administrator created user accounts, are incorrectly assigned to groups that allow higher system-level privileges than intended for those user accounts. Depending on the usage of these accounts, this may lead to full system compromise.

Weakness: CWE-281 (Improper Preservation of Permissions)

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


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

No fix has been published for CVE-2024-52869 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-52869 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52869 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52869 is a medium-severity vulnerability in n/a, published on 8 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52869 exists.

Affected product: n/a. 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-52869/ (Markdown: https://insights.sbomify.com/CVE-2024-52869/index.md)
```

## Sources

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

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