# CVE-2023-47480: Privilege escalation in n/a

> A local attacker can escalate privileges in Pure Data due to improper handling of set*id functions, requiring an upgrade to the fixed version.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 20 Sep 2024
- **Updated:** 25 Sep 2024
- **Also known as:** DEBIAN-CVE-2023-47480, DLA-3895-1, GHSA-7xv2-675g-4wq2, UBUNTU-CVE-2023-47480

## What is CVE-2023-47480?

CVE-2023-47480 is a high-severity vulnerability in n/a, published on 20 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Pure Data 0.54-0 and fixed in 0.54-1 allows a local attacker to escalate privileges via the set*id () function.

Weakness: CWE-252 (Unchecked Return Value)

## Which versions are affected by CVE-2023-47480?


## How do I fix CVE-2023-47480?

Upgrade to a fixed version.

## Is CVE-2023-47480 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47480 and fix it if it is affected.

What it is: CVE-2023-47480 is a high-severity vulnerability in n/a, published on 20 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-47480 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-2023-47480/ (Markdown: https://insights.sbomify.com/CVE-2023-47480/index.md)
```

## Sources

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

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