Skip to content

extract_signed_shortcut can be raced to disclose process memory

Low
0xilis published GHSA-9mp6-ph4g-6cgq May 7, 2024

Package

libshortcutsign (misc)

Affected versions

4acc70eece6a07937a3e94978f8f4412763c59c5

Patched versions

a2f6753ae106c292ddbfb601c9ecb116785666bf

Description

Impact

extract_signed_shortcut has a race condition which may lead to disclosure of process memory. This is as a file can be modified to be smaller after binary_size is saved but before the bytes finish copying. This may result in the buffer having leftover bytes.

Patches

The issue has been patched in a recent commit on May 7 2024 EST. It can be viewed here: a2f6753

Severity

Low

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
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

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:L/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses

Credits