# CVE-2024-25763: Use after free in n/a

> A use-after-free vulnerability in openNDS allows attackers to potentially execute arbitrary code or cause a denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Feb 2024
- **Updated:** 6 Dec 2024
- **Also known as:** DEBIAN-CVE-2024-25763, GHSA-jrrc-pqj2-c99f, UBUNTU-CVE-2024-25763, USN-7312-1

## What is CVE-2024-25763?

CVE-2024-25763 is a medium-severity use after free vulnerability in n/a, published on 26 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

openNDS 10.2.0 is vulnerable to Use-After-Free via /openNDS/src/auth.c.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Opennds Opennds.

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

Upgrade to a fixed version.

## Is CVE-2024-25763 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-38317](https://insights.sbomify.com/CVE-2023-38317/): Command injection in n/a (critical 9.8)
- [CVE-2023-38318](https://insights.sbomify.com/CVE-2023-38318/): Command injection in n/a (critical 9.8)
- [CVE-2023-38319](https://insights.sbomify.com/CVE-2023-38319/): Command injection in n/a (critical 9.8)
- [CVE-2023-38323](https://insights.sbomify.com/CVE-2023-38323/): Command injection in n/a (critical 9.8)
- [CVE-2023-41101](https://insights.sbomify.com/CVE-2023-41101/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25763 is a medium-severity use after free vulnerability in n/a, published on 26 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-25763 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-25763/ (Markdown: https://insights.sbomify.com/CVE-2024-25763/index.md)
```

## Sources

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

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