Skip to content

LibOSDP vulnerable to a null pointer deref in osdp_reply_name

Moderate severity GitHub Reviewed Published Mar 7, 2024 in goToMain/libosdp • Updated Aug 11, 2024

Package

pip libosdp (pip)

Affected versions

< 2.4.0

Patched versions

2.4.0

Description

Issue:

At ospd_common.c, on the osdp_reply_name function, any reply id between REPLY_ACK and REPLY_XRD is valid, but names array do not declare all of the range. On a case of an undefined reply id within the range, name will be null (name = names[reply_id - REPLY_ACK];). Null name will casue a crash on next line: if (name[0] == '\0') as null[0] is invalid.

Attack:

As this logic is not limited to a secure connection, attacker may trigger this vulnerability without any prior knowledge.

Impact

Denial of Service

Patch

The issue has been patched in 24409e98a260176765956ec766a04cb35984fab1

References

@sidcha sidcha published to goToMain/libosdp Mar 7, 2024
Published to the GitHub Advisory Database Mar 8, 2024
Reviewed Mar 8, 2024
Last updated Aug 11, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-7945-5mcv-f2pp

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.