CyberSecBulletin
CVE-2013-2597Exploited in the wildNVD status: Analyzed

Code Aurora ACDB Audio Driver Stack-based Buffer Overflow

CVE-2013-2597 is a high-severity stack-based buffer overflow vulnerability in Android-msm from Codeaurora, with a CVSS 2.0 base score of 7.2 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. Affected Android-msm versions: 2.6.29; 3.2.54; 3.2.55, and others listed below. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on September 15, 2022, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Check which version of Android-msm you run against the affected versions below, and install the vendor's latest release.
  2. CISA's required action: Apply updates per vendor instructions.

Affected products and versions

VendorProductAffected versionsFixed in
CodeauroraAndroid-msm2.6.29; 3.2.54; 3.2.55; 3.2.56; 3.2.57; 3.2.58; 3.2.59; 3.2.60; and 32 more rangesNot stated

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Access vector
LocalLocal access is required.
Access complexity
LowNo special conditions are needed.
Authentication
NoneNo login is needed.
Confidentiality
CompleteAll data can be read.
Integrity
CompleteAny data can be modified.
Availability
CompleteThe system can be shut down completely.

Vector: AV:L/AC:L/Au:N/C:C/I:C/A:C. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.4HighCISA (ADP)
CVSS 2.07.2HighNVD

Official description

Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Stack-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the stack.

How developers prevent this class of flaw

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Implement and perform bounds checking on input.

More Stack-based Buffer Overflow vulnerabilities (CWE-121)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Spotted an error? Tell us.