openNDS 10.2.0 /openNDS/src/auth.c use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in openNDS 10.2.0. This affects an unknown function of the file /openNDS/src/auth.c. Performing a manipulation results in use after free. This vulnerability is reported as CVE-2024-25763. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, was found in openNDS 10.2.0. This affects some unknown processing of the file /openNDS/src/auth.c. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. The impact remains unknown. The summary by CVE is:

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

The weakness was disclosed 02/26/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-25763 since 02/12/2024. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 227827 (Linux Distros Unpatched Vulnerability : CVE-2024-25763), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (227827). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 5.5
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 227827
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2024-25763

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/12/2024 🔍
02/26/2024 +14 days 🔍
02/26/2024 +0 days 🔍
03/06/2025 +374 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2024-25763 (🔍)
GCVE (CVE): GCVE-0-2024-25763
GCVE (VulDB): GCVE-100-254757

Entryinfo

Created: 02/26/2024 16:55
Updated: 03/06/2025 08:36
Changes: 02/26/2024 16:55 (35), 12/06/2024 22:23 (27), 03/06/2025 08:36 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!