CVE-2012-1350
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCisco IOS 12.3 and 12.4 on Aironet access points allows remote attackers to cause a denial of service (radio-interface input-queue hang) via IAPP 0x3281 packets, aka Bug ID CSCtc12426.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDenial of service vulnerability in Cisco IOS 12.3 and 12.4 on Aironet wireless access points allows remote attackers to cause the radio-interface input queue to hang by sending specially crafted IAPP (Inter-Access Point Protocol) packets with opcode 0x3281.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.3= 12.3\(1a\)= 12.3\(2\)ja= 12.3\(2\)ja5= 12.3\(2\)jk= 12.3\(2\)jk1= 12.3\(2\)t3= 12.3\(2\)t8= 12.3\(2\)xa4= 12.3\(2\)xa5= 12.3\(2\)xc1= 12.3\(2\)xc2all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Aironet access point modelExecute 'show version' or 'show inventory' on the device and look for model identifiers: 1040, 1140, 1260, 3500, 3600, 600 Office Extend, or Ap1100Affected if Device model matches any of the listed Aironet series models (1040, 1140, 1260, 3500, 3600, 600, Ap1100)
-
Check IOS versionExecute 'show version' and locate the IOS release number in the output. Compare against the affected 12.3 and 12.4 version branchesAffected if IOS version begins with 12.3 or 12.4, especially the specific versions listed (12.3, 12.3(1a), 12.3(2)ja, etc.)
-
Verify IAPP protocol is enabledExecute 'show running-config | include iapp' or 'show protocol' to check if Inter-Access Point Protocol is configured on the access pointAffected if IAPP protocol is actively enabled on the device configuration
-
Check radio interface statusExecute 'show interface' for the radio interfaces (e.g., 'show interface dot11radio0') and look for indicators of input queue hang or severe packet queue buildupAffected if Radio interface shows abnormally high input queue depth or appears hung with no traffic throughput
The device is likely affected if it is any Aironet model (1040/1140/1260/3500/3600/600/Ap1100) running IOS 12.3 or 12.4 with IAPP protocol enabled, and the radio interface exhibits queue hang symptoms.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Cisco IOS on affected Aironet access points to a patched version that addresses Bug ID CSCtc12426; until then, consider network segmentation or filtering to block unauthorized IAPP traffic.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-1350 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data