Threats / Code Aurora / CVE-2013-2597

CVE-2013-2597 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-19

Code Aurora ACDB Audio Driver vulnerability

Stack-based buffer overflow in Code Aurora ACDB Audio Driver enables privilege escalation. Vulnerability has been exploited in the wild.

Verdict

Today item — known-exploited.

A stack buffer overflow in the ACDB audio driver allows attackers to escalate privileges on affected systems. The vulnerability has demonstrated active exploitation, though ransomware campaigns have not been associated with it.

CISA KEV Yes · 2022-09-15⁴EPSS 0.01503 (verify live)⁵Exploit Weaponized · public PoC⁶CVSS 8.4 (CISA)³CISA SSVC Exploitation: active · Automatable: no · Impact: total³

Is it exploitable?

— the evidence, ranked above the score

Exploit available

Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.

vulncheck.com ↗Confirmed

Reported exploitation

1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

cisa.gov ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-09-15).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.01503 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 8.4 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Code Aurora, ACDB Audio Driver. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.

CISA-ADP ↗Reported

Weakness (CWE)

Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.

NVD ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog 2937 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

WeaknessCWE-119 · Memory Buffer Bounds ErrorMemory safety

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Front door — unauthenticated access narrative 1

Attacker

I craft malicious input to overflow the stack buffer in the audio driver.

Business

Attacker gains elevated privileges on the device, bypassing security controls.

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker

I leverage the privilege escalation to execute arbitrary code with kernel-level access.

Business

System integrity is compromised; attacker can install persistent malware or access sensitive data.

Lateral reach — past segmentation narrative 3

Attacker

I maintain persistence across reboots through kernel-level implants.

Business

Long-term compromise of affected devices creates ongoing operational and data security risk.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

Weaponized exploit available (VulnCheck)

1 reported-exploitation source(s)

CVSS 8.4 — CISA-assigned (CVE.org ADP)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping (NVD feed — CNA left none)

Public exploit availability

Catalogued by mitre (CNA)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

No finder is named in the public CVE record — attribution scoped to the sources checked.

Disclosure & credit²

Catalogued by mitreCNA

Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2013-2597.html"], ["v", "sha256:6c72a72b20d38ba3de71db12451dd79b184e3a8fa079a8d4d6a2880387b25e61"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.