dbcve.org
Content Services Switch 11500Hardware / appliance · Cisco

CVE-2010-2629

HIGH · 7.5 CVSS v2.0 Published 2010-07-06
Fix available
A fix is available. Upgrade to after 8.20.3.03 or later.
See remediation →
84/100
Remediation priority · High
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
The Cisco Content Services Switch (CSS) 11500 with software 8.20.4.02 and the Application Control Engine (ACE) 4710 with software A2(3.0) do not properly handle LF header terminators in situations where the GET line is terminated by CRLF, which allows remote attackers to conduct HTTP request smuggling attacks and possibly bypass intended header insertions via crafted header data, as demonstrated by an LF character between the ClientCert-Subject and ClientCert-Subject-CN headers. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-1576.

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

HTTP request smuggling vulnerability in Cisco CSS 11500 and ACE 4710 where improper handling of LF header terminators when GET requests use CRLF allows attackers to inject crafted headers and bypass security controls via ClientCert-Subject header manipulation. This is an incomplete fix for CVE-2010-1576.

MitigationApply vendor patches for both CSS and ACE devices; if patching is not immediately feasible, implement strict validation at upstream proxies and monitor for anomalous HTTP traffic patterns indicative of request smuggling.

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
Content Services Switch 11500Hardware / appliance
Affected:<= 8.20.3.03= 8.20.0.01= 08.20.1.01= 8.20.1.01= 8.20.2.01
Ace 4710Hardware / appliance
Affected:<= a3\(2.5\)= a1\(2.0\)= a1\(8.0\)

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
Partial

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

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

  1. Identify the device model
    Log into the device CLI or web interface and verify the hardware model is Cisco CSS 11500 or Cisco ACE 4710.
    Affected if Device is not one of these two models, the vulnerability does not apply.
  2. Check the installed software version
    Execute the command to display the software/firmware version (typically 'show version' or similar in the device CLI). Compare the version number against the affected ranges: CSS 11500 versions <= 8.20.3.03, 8.20.0.01, 08.20.1.01, 8.20.1.01, 8.20.2.01; ACE 4710 versions <= a3(2.5), a1(2.0), a1(8.0).
    Affected if The installed version matches or is lower than any of the listed affected versions.
  3. Verify Client Certificate authentication is enabled
    Inspect the device configuration for ClientCert authentication settings. Look for SSL/TSL profile configurations that enable client certificate verification, specifically settings related to ClientCert-Subject header processing.
    Affected if Client Certificate authentication is enabled and the device processes the ClientCert-Subject header, creating the attack surface for header injection.
  4. Inspect HTTP profile for header handling configuration
    Review the HTTP profile or virtual server configuration for how headers are processed. Check for any custom header manipulation rules or settings that control CRLF/LF interpretation in HTTP requests.
    Affected if The HTTP profile allows non-strict header parsing or does not reject malformed headers with inconsistent line terminators.
  5. Check for anomalous HTTP traffic patterns
    Review access logs and traffic logs for requests containing CRLF injection patterns, especially in the ClientCert-Subject field or other header fields that appear to have unexpected line breaks.
    Affected if Traffic logs show HTTP requests with malformed headers or evidence of header injection attempts.

The environment is affected if the device is a Cisco CSS 11500 or ACE 4710 running an affected software version AND Client Certificate authentication with ClientCert-Subject header processing is enabled.

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
Upgrade available Upgrade to a release after 8.20.3.03
Interim mitigation

Apply vendor patches for both CSS and ACE devices; if patching is not immediately feasible, implement strict validation at upstream proxies and monitor for anomalous HTTP traffic patterns indicative of request smuggling.

Fix this in Content Services Switch 11500 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2629 — 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-2010-2629 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