Skip to main content
VulnerabilityPublished Updated

CVE-2024-25763: openNDS · Use After Free

Affects openNDSSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHublumingyindetect/openNDSpkg:github/lumingyindetect/openNDSOther threatsAffected
  • =10.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Conduct a thorough code review of the auth.c component to identify and fix the use-after-free condition, ideally by updating to a patched version once available.
  2. Implement strict memory management and validation checks to prevent dangling pointers and ensure freed memory is not accessed.
  3. Restrict network exposure of openNDS authentication services to trusted networks only, using firewalls and network segmentation.
  4. Enforce the principle of least privilege to limit the ability of attackers to gain the required privileges for exploitation.
  5. Monitor authentication logs and system behavior for anomalies indicative of exploitation attempts or crashes.
  6. Employ runtime protections such as AddressSanitizer or similar memory error detection tools during development and testing.
  7. Prepare incident response plans specifically addressing potential authentication service disruptions.
  8. Stay updated with vendor advisories for patches or official mitigations and apply them promptly when released.

Description

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

References

Community reviews

Loading reviews…