iOSOperating system · Cisco

CVE-2012-5422

MEDIUM · 6.8 CVSS v2.0 Published 2014-04-23
Fix available
A fix is available. Upgrade to after 15.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Unspecified vulnerability in Cisco IOS before 15.3(2)T on AS5400 devices allows remote authenticated users to cause a denial of service (spurious errors) via unknown vectors, aka Bug ID CSCub61009.

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 confidence

Vulnerability in Cisco IOS before version 15.3(2)T on AS5400 series devices allows remote authenticated users to cause denial of service through unspecified vectors that trigger spurious errors. The attack requires valid credentials, suggesting exploitation involves sending malformed requests to the device.

MitigationUpgrade Cisco IOS on AS5400 devices to version 15.3(2)T or later to address the vulnerability. Ensure only trusted, authenticated users have administrative access to the device.

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
iOSOperating system
Affected:<= 15.3\(2\)s= 15.3
As5400 Universal GatewayHardware / appliance
Affected:all versions
As5400hpx Universal GatewayHardware / appliance
Affected:all versions
As5400xm Media GatewayHardware / appliance
Affected:all versions
As5400xm Universal GatewayHardware / appliance
Affected:all versions

CVSS 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
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:S/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Run 'show version' or 'show hardware' command and look for AS5400, AS5400hpx, AS5400xm, or similar AS5400 series designation in the output
    Affected if The device model is any variant of Cisco AS5400 Universal Gateway, AS5400hpx Universal Gateway, AS5400xm Media Gateway, or AS5400xm Universal Gateway
  2. Check the Cisco IOS version
    Run 'show version' command and locate the IOS version number in the output (typically displayed as something like 15.3(1)T or 15.3)
    Affected if The IOS version is 15.3, 15.3(2)s, or any version earlier than 15.3(2)T, or if the version cannot be determined but the device is an AS5400 series (all versions of AS5400 are affected)
  3. Verify remote management access is enabled
    Run 'show running-config | include ip http|ip ssh|telnet' or check the configuration with 'show running-config' for lines enabling HTTP (ip http server), SSH (ip ssh), or Telnet access
    Affected if HTTP, SSH, or Telnet remote management is enabled, as the vulnerability requires authenticated remote access to send malformed requests
  4. Confirm authentication is configured
    Run 'show running-config | include aaa|username' to check if local or remote authentication (AAA) is configured, and verify valid user accounts exist
    Affected if Authentication methods are configured with valid user accounts, as the vulnerability requires authenticated users to trigger the denial of service

The environment is affected if the device is any Cisco AS5400 series model running Cisco IOS version 15.3 or earlier (including 15.3(2)s) AND remote authenticated access is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 15.3
Interim mitigation

Upgrade Cisco IOS on AS5400 devices to version 15.3(2)T or later to address the vulnerability. Ensure only trusted, authenticated users have administrative access to the device.

Fix this in iOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-5422 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-5422 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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