dbcve.org
iOSOperating system · Cisco

CVE-2011-0348

MEDIUM · 6.4 CVSS v2.0 Published 2011-01-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Cisco IOS 12.4(11)MD, 12.4(15)MD, 12.4(22)MD, 12.4(24)MD before 12.4(24)MD3, 12.4(22)MDA before 12.4(22)MDA5, and 12.4(24)MDA before 12.4(24)MDA3 on the Cisco Content Services Gateway Second Generation (aka CSG2) allows remote attackers to bypass intended access restrictions and intended billing restrictions by sending HTTP traffic to a restricted destination after sending HTTP traffic to an unrestricted destination, aka Bug ID CSCtk35917.

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 confidence

The Cisco Content Services Gateway Second Generation (CSG2) has a logic flaw where the device fails to properly enforce access and billing restrictions when HTTP traffic is sent to a restricted destination after an unrestricted destination. This allows unauthenticated remote attackers to bypass intended policy controls through a specific request sequence.

MitigationUpgrade Cisco IOS on the CSG2 to version 12.4(24)MD3, 12.4(22)MDA5, 12.4(24)MDA3 or later as specified in the advisory. If the device cannot be upgraded, implement upstream network filtering to restrict the attacker's ability to send the specific HTTP request sequence.

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:= 12.4\(11\)md= 12.4\(15\)md= 12.4\(22\)md= 12.4\(22\)mda= 12.4\(24\)md= 12.4\(24\)md1= 12.4\(24\)mda

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
None
Confidentiality
Partial
Integrity
Partial
Availability
None

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

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

  1. Confirm device is a Cisco CSG2
    Log into the device and run 'show hardware' or 'show version' to identify the device model. Look for 'Cisco Content Services Gateway Second Generation' or 'CSG2' in the output.
    Affected if Device model is not CSG2 - the vulnerability only affects CSG2 devices
  2. Check Cisco iOS version
    Run 'show version' and locate the iOS version string (for example, 12.4(24)md). Compare this version against the affected versions: 12.4(11)md, 12.4(15)md, 12.4(22)md, 12.4(22)mda, 12.4(24)md, 12.4(24)md1, 12.4(24)mda.
    Affected if iOS version matches one of the affected versions listed above - older 12.4 MD/MDA versions are vulnerable
  3. Verify HTTP policy enforcement is configured
    Run 'show running-config | include http' or access the CSG2 management interface to check if HTTP traffic handling and policy rules are configured for content billing or access control.
    Affected if HTTP policy enforcement is configured - the vulnerability allows bypassing these policies through a specific request sequence
  4. Review policy enforcement logs for bypass attempts
    Check CSG2 logs using 'show logging' or the management interface for any instances where restricted HTTP destinations were accessed after unrestricted destinations, indicating the bypass may have been attempted.
    Affected if Logs show unauthorized HTTP traffic to restricted destinations following unrestricted ones - indicates active exploitation or attempt

The environment is affected if the device is a Cisco CSG2 running an affected iOS version (12.4 MD/MDA variants listed) with HTTP policy controls configured, and the specific request sequence could be or has been used to bypass those controls.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco IOS on the CSG2 to version 12.4(24)MD3, 12.4(22)MDA5, 12.4(24)MDA3 or later as specified in the advisory. If the device cannot be upgraded, implement upstream network filtering to restrict the attacker's ability to send the specific HTTP request sequence.

Fix this in iOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-0348 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2011-0348 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