# CVE-2005-4514: Security feature bypass in n/a

> Attackers can bypass malicious token detection in Webwasher CSM Appliance Suite by using case variations, evading security filters.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2cpf-rv8p-fqqc

## What is CVE-2005-4514?

CVE-2005-4514 is a medium-severity vulnerability in n/a, published on 23 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The encapsulation script mechanism in Webwasher CSM Appliance Suite 5.x uses case-sensitive detection of malicious tokens, which allows attackers to bypass script detection by using tokens that can be upper or lower case.  NOTE: the vendor has stated that this problem could not be reproduced, and has asked the researcher for more information, without a response as of 20060103

## Which versions are affected by CVE-2005-4514?

It affects 1 product.


Products: Webwasher Csm Appliance Suite.

## How do I fix CVE-2005-4514?

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

## Is CVE-2005-4514 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4514 and fix it if it is affected.

What it is: CVE-2005-4514 is a medium-severity vulnerability in n/a, published on 23 Dec 2005. 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-2005-4514 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-2005-4514/ (Markdown: https://insights.sbomify.com/CVE-2005-4514/index.md)
```

## Sources

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

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