CVE-2014-3399
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 SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.2(.2.4) and earlier does not properly manage session information during creation of a SharePoint handler, which allows remote authenticated users to overwrite arbitrary RAMFS cache files or inject Lua programs, and consequently cause a denial of service (portal outage or system reload), via crafted HTTP requests, aka Bug ID CSCup54208.
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 confidenceThe SSL VPN in Cisco ASA Software 9.2(.2.4) and earlier fails to properly manage session information when creating SharePoint handlers, allowing authenticated remote users to overwrite arbitrary RAMFS cache files or inject Lua programs via crafted HTTP requests, causing portal outages or system reloads.
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<= 9.2\(2.4\)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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:N/I:P/A:P
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 Cisco ASA Software versionLog into the ASA CLI and run 'show version' or use ASDM to view the system software versionAffected if The installed version is 9.2(x) where x is 2.4 or lower, or any version in the 9.2 branch <= 9.2(2.4)
-
Verify SSL VPN is enabledCheck ASA configuration for any VPN-related settings using 'show running-config | include vpn' or via ASDM under Configuration > Remote Access VPNAffected if Any SSL VPN (clientless or AnyConnect) is active on the device
-
Confirm SharePoint handler is configuredExamine the SSL VPN portal configuration for SharePoint integration using 'show running-config webvpn' or check for sharepoint-related settings in the VPN portal profileAffected if SharePoint handler or any SharePoint-related webvpn features are configured on the SSL VPN portal
-
Inspect for unauthorized Lua scripts or cache anomaliesUse 'show file' commands or access the ASA file system via ' privileged exec mode to check for unexpected Lua program files in the cache or RAMFS storage areasAffected if Unexpected Lua scripts exist in the VPN cache or unusual modifications to RAMFS cache files are found
You are affected if your Cisco ASA runs version 9.2(2.4) or earlier AND has SSL VPN with SharePoint handler enabled, as the vulnerability requires the SSL VPN SharePoint feature to be configured.
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 Software to a version beyond 9.2(.2.4) that addresses CVE-2014-3399; given this is a session management flaw in the SSL VPN, ensure only authorized users have VPN access and monitor for anomalous HTTP requests to the SharePoint handler.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3399 — 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-3399 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