CVE-2013-2597
Published: September 15, 2022
Official Description
The Code Aurora audio calibration database (acdb) audio driver contains a stack-based buffer overflow vulnerability that allows for privilege escalation. Code Aurora is used in third-party products such as Qualcomm and Android.
CISA KEV Advisory
Code Aurora ACDB Audio Driver Stack-based Buffer Overflow Vulnerability
The Code Aurora audio calibration database (acdb) audio driver contains a stack-based buffer overflow vulnerability that allows for privilege escalation. Code Aurora is used in third-party products such as Qualcomm and Android.
Apply updates per vendor instructions.
Risk Analysis
The Code Aurora audio calibration database (acdb) audio driver contains a stack-based buffer overflow, allowing for privilege escalation. Given its inclusion in CISA's KEV catalog and an EPSS score of 0.06744, this vulnerability presents a high and urgent risk of exploitation.
This vulnerability is actively being exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
Users of devices utilizing Code Aurora audio drivers, such as Qualcomm and Android, should apply available updates to patch this privilege escalation vulnerability.
Technical Analysis
CVE-2013-2597 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2013-2597 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (2)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2013-2597 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1