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

> An authenticated attacker can create symlinks to read sensitive files via root-privileged debug log collection on Alcatel-Lucent deskphones.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 7 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6jj6-4cwr-qpr2

## What is CVE-2024-29150?

CVE-2024-29150 is a high-severity vulnerability in n/a, published on 7 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Alcatel-Lucent ALE NOE deskphones through 86x8_NOE-R300.1.40.12.4180 and SIP deskphones through 86x8_SIP-R200.1.01.10.728. Because of improper privilege management, an authenticated attacker is able to create symlinks to sensitive and protected data in locations that are used for debugging files. Given that the process of gathering debug logs is carried out with root privileges, any file referenced in the symlink is consequently written to the debug archive, thereby granting accessibility to the attacker.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-29150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29150 is a high-severity vulnerability in n/a, published on 7 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29150 in the wild and no public exploit code.

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

## Sources

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

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