CVE-2026-48065: CWE-122: Heap-based Buffer Overflow in mcdope pam_usb
A heap-based buffer overflow vulnerability exists in pam_usb versions prior to 0.9.1 due to improper heap memory allocation when processing the number of devices from the configuration file. On 32-bit systems, integer overflow causes an undersized allocation, leading to heap overflow during array writes. This vulnerability has a CVSS score of 6.7 and can impact confidentiality, integrity, and availability. The issue is fixed in version 0.9.1.
AI Analysis
Technical Summary
The vulnerability in pam_usb before version 0.9.1 arises from the src/conf.c source file allocating heap memory proportional to n_devices, a count derived from libxml2 XPath evaluation of the configuration file, without enforcing an upper bound. On 32-bit architectures like armv7l and i686, the multiplication n_devices * sizeof(t_pusb_device) overflows size_t, resulting in a small allocation size passed to xmalloc(). Since xmalloc() only aborts on NULL returns and accepts small non-NULL allocations, subsequent writes overflow the heap buffer. This is a classic heap-based buffer overflow (CWE-122) triggered by integer overflow (CWE-190). The vulnerability is resolved in pam_usb version 0.9.1.
Potential Impact
Successful exploitation can lead to heap-based buffer overflow, potentially allowing an attacker with local privileges to execute arbitrary code, cause denial of service, or escalate privileges. The CVSS vector indicates local attack vector with low complexity, requiring high privileges and no user interaction, impacting confidentiality, integrity, and availability. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
Upgrade pam_usb to version 0.9.1 or later, where this vulnerability is fixed. Since the vendor advisory or patch links are not provided, verify the version in use and apply the official update from the mcdope project to remediate this issue. Patch status is not explicitly confirmed beyond the fix in 0.9.1; check the vendor's official resources for the latest remediation guidance.
CVE-2026-48065: CWE-122: Heap-based Buffer Overflow in mcdope pam_usb
Description
A heap-based buffer overflow vulnerability exists in pam_usb versions prior to 0.9.1 due to improper heap memory allocation when processing the number of devices from the configuration file. On 32-bit systems, integer overflow causes an undersized allocation, leading to heap overflow during array writes. This vulnerability has a CVSS score of 6.7 and can impact confidentiality, integrity, and availability. The issue is fixed in version 0.9.1.
CVSS v3.1
Score 6.7medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in pam_usb before version 0.9.1 arises from the src/conf.c source file allocating heap memory proportional to n_devices, a count derived from libxml2 XPath evaluation of the configuration file, without enforcing an upper bound. On 32-bit architectures like armv7l and i686, the multiplication n_devices * sizeof(t_pusb_device) overflows size_t, resulting in a small allocation size passed to xmalloc(). Since xmalloc() only aborts on NULL returns and accepts small non-NULL allocations, subsequent writes overflow the heap buffer. This is a classic heap-based buffer overflow (CWE-122) triggered by integer overflow (CWE-190). The vulnerability is resolved in pam_usb version 0.9.1.
Potential Impact
Successful exploitation can lead to heap-based buffer overflow, potentially allowing an attacker with local privileges to execute arbitrary code, cause denial of service, or escalate privileges. The CVSS vector indicates local attack vector with low complexity, requiring high privileges and no user interaction, impacting confidentiality, integrity, and availability. There are no known exploits in the wild as of the published date.
Mitigation Recommendations
Upgrade pam_usb to version 0.9.1 or later, where this vulnerability is fixed. Since the vendor advisory or patch links are not provided, verify the version in use and apply the official update from the mcdope project to remediate this issue. Patch status is not explicitly confirmed beyond the fix in 0.9.1; check the vendor's official resources for the latest remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-20T18:25:25.707Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a17519de29bf47b50e771b7
Added to database: 05/27/2026, 20:18:37 UTC
Last enriched: 06/03/2026, 20:53:29 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 61
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.