CVE-2011-3299
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 Appliances (ASA) 5500 series devices, and the ASA Services module in Cisco Catalyst 6500 series devices, with software 7.0 before 7.0(8.13), 7.1 and 7.2 before 7.2(5.4), 8.0 before 8.0(5.25), 8.1 and 8.2 before 8.2(5.11), 8.3 before 8.3(2.23), 8.4 before 8.4(2.6), and 8.5 before 8.5(1.1) and Cisco Firewall Services Module (aka FWSM) 3.1 before 3.1(21), 3.2 before 3.2(22), 4.0 before 4.0(16), and 4.1 before 4.1(7) allow remote attackers to cause a denial of service (device reload) via crafted SunRPC traffic, aka Bug IDs CSCto92380 and CSCtq09972.
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 5500 series and FWSM devices contain a vulnerability in the SunRPC inspection handling code. Remote attackers can send specially crafted SunRPC packets to the device, causing it to reload unexpectedly. This is a Denial of Service (DoS) vulnerability requiring no authentication.
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= 7.0= 7.0\(0\)= 7.0\(1\)= 7.0\(2\)= 7.0\(4\)= 7.0\(5\)= 7.0\(5.2\)= 7.0\(6\)= 7.0\(6.7\)= 7.0\(7\)= 7.0\(8\)= 7.0.1all versionsall versions= 3.1= 3.1\(2\)= 3.1\(3\)= 3.1\(4\)= 3.1\(5\)= 3.1\(6\)= 3.1\(7\)= 3.1\(8\)= 3.1\(9\)= 3.1\(10\)= 3.1\(11\)= 3.1\(12\)all 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 device modelUse 'show version' or 'show hardware' command to confirm the device is a Cisco ASA 5500 series, ASA 5500-X series, or Firewall Services Module (FWSM) running on Catalyst 6500/7600Affected if Device is an ASA 5500 series, ASA 5500-X series, or FWSM on Catalyst 6500/7600
-
Check ASA software versionExecute 'show version' and locate the 'Cisco Adaptive Security Appliance Software' version line. Compare against affected 7.0.x versions or note that all versions of ASA 5500 are affectedAffected if Version is 7.0.x (specifically 7.0 through 7.0.1) or any version of Cisco ASA 5500 series
-
Check FWSM software versionExecute 'show version' on the FWSM and compare against affected 3.1.x versions (3.1 through 3.1(12))Affected if FWSM version is 3.1.x through 3.1(12)
-
Verify SunRPC inspection is enabledExecute 'show service-policy' or examine the running configuration for 'inspect sunrpc' applied to an interface or traffic classAffected if SunRPC inspection is configured and active on an interface
Device is affected if it is an ASA 5500 series or FWSM with a vulnerable software version AND SunRPC inspection is enabled in the configuration
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 version 7.0(8.13), 7.2(5.4), 8.0(5.25), 8.2(5.11), 8.3(2.23), 8.4(2.6), 8.5(1.1) or later; FWSM to 3.1(21), 3.2(22), 4.0(16), or 4.1(7) or later. As a workaround, block SunRPC (port 111) traffic at the perimeter.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3299 — 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-2011-3299 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