# CVE-2010-1575: Auth bypass in n/a

> Remote attackers can bypass authentication on Cisco Content Services Switches by injecting crafted ClientCert headers, allowing unauthorized access.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-crxp-64qq-hp9c

## What is CVE-2010-1575?

CVE-2010-1575 is a high-severity authentication bypass vulnerability in n/a, published on 6 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Cisco Content Services Switch (CSS) 11500 with software 08.20.1.01 conveys authentication data through ClientCert-* headers but does not delete client-supplied ClientCert-* headers, which might allow remote attackers to bypass authentication via crafted header data, as demonstrated by a ClientCert-Subject-CN header, aka Bug ID CSCsz04690.

Weakness: CWE-264

## Which versions are affected by CVE-2010-1575?

It affects 1 product.


Products: Cisco Content Services Switch 11500.

## How do I fix CVE-2010-1575?

No fix has been published for CVE-2010-1575 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-1575 being exploited?

There is no known exploitation of CVE-2010-1575 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-1631](https://insights.sbomify.com/CVE-2006-1631/): Denial of service in n/a (medium 5.0)
- [CVE-2005-3426](https://insights.sbomify.com/CVE-2005-3426/): Memory corruption in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-1575 and fix it if it is affected.

What it is: CVE-2010-1575 is a high-severity authentication bypass vulnerability in n/a, published on 6 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-1575 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-1575/ (Markdown: https://insights.sbomify.com/CVE-2010-1575/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-1575
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-1575
- OSV: https://osv.dev/vulnerability/CVE-2010-1575

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-1575/
Summaries are generated and may contain mistakes; the official description above is the record.