Asa Cx Context Aware SecurityApplication · Cisco
CVE-2012-4629
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 · uneditedThe Cisco ASA-CX Context-Aware Security module before 9.0.2-103 for Adaptive Security Appliances (ASA) devices, and Prime Security Manager (aka PRSM) before 9.0.2-103, allows remote attackers to cause a denial of service (disk consumption and application hang) via unspecified IPv4 packets that trigger log entries, aka Bug ID CSCub70603.
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 · high confidenceThis vulnerability in Cisco ASA-CX and Prime Security Manager allows remote attackers to cause denial of service via specially crafted IPv4 packets that trigger excessive log entries. The uncontrolled logging consumes disk space and causes the application to hang, rendering the security devices non-functional.
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
Asa Cx Context Aware SecurityApplication
<= 9.0
Prime Security ManagerApplication
<= 9.0CVSS 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 installed Cisco ASA-CX versionAccess the ASA-CX management console or use the 'show version' command via CLI to retrieve the software version numberAffected if The displayed version is 9.0 or earlier (any version <= 9.0)
-
Identify installed Cisco Prime Security Manager versionAccess the Prime Security Manager interface or check the software package version installed on the management serverAffected if The displayed version is 9.0 or earlier (any version <= 9.0)
-
Compare versions to affected rangeIf you maintain an inventory of installed software, verify that neither product is at version 9.0 or belowAffected if Either product is at version 9.0 or lower in your environment
-
Assess network exposure of the deviceDetermine if the ASA-CX or Prime Security Manager management interface is accessible from network segments where untrusted IPv4 traffic could be receivedAffected if The device is network-reachable and could receive specially crafted IPv4 packets from unauthenticated remote sources
You are affected if either Cisco ASA-CX or Prime Security Manager is installed at version 9.0 or lower and the device is exposed to network traffic where attackers could send specially crafted IPv4 packets.
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 ASA-CX Context-Aware Security module and Prime Security Manager to version 9.0.2-103 or later to remediate this vulnerability. Additionally, implement network segmentation and access controls to limit exposure to unauthenticated remote attackers.
Fix this in Asa Cx Context Aware Security
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4629 — 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-4629 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