Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2014-2181
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 Adaptive Security Appliance (ASA) Software allows remote authenticated users to read files by sending a crafted URL to the HTTP server, as demonstrated by reading the running configuration, aka Bug ID CSCun78551.
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 confidenceCisco ASA Software contains an information disclosure vulnerability in its built-in HTTP server. A remote authenticated attacker can send a crafted URL to read arbitrary files on the device, including the running configuration, through the HTTP management interface.
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
Adaptive Security Appliance SoftwareOperating system
all 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
- Single
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:S/C:C/I:N/A:N
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.
-
Verify ASA device and versionExecute 'show version' on the ASA CLI to confirm the device is Cisco ASA Software and note the version numberAffected if The device is a Cisco ASA and the HTTP server feature is enabled
-
Confirm HTTP server is enabledExecute 'show running-config | include http' to check if the HTTP server is enabled and configuredAffected if HTTP server is enabled (output shows 'http server enable' or http configuration)
-
Check HTTP server listening interfaceExecute 'show running-config http' to see which interfaces have HTTP management enabledAffected if HTTP is enabled on any interface (especially outside/untrusted interfaces)
-
Verify HTTP access controlReview 'show running-config | include http' for 'http 0.0.0.0 0.0.0.0' which allows unrestricted HTTP access, or check specific 'http' ACL entriesAffected if HTTP access is allowed from any/untrusted networks (0.0.0.0/0) or from networks you do not control
You are affected if you have the Cisco ASA HTTP server enabled and it is accessible from networks you do not exclusively control, regardless of version since all versions are vulnerable.
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 dataDisable the HTTP server feature on the ASA if not required for management, or restrict HTTP access to trusted management IP addresses via ACLs. Apply the Cisco patch when available.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2181 — 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-2014-2181 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