# CVE-2007-2734: Security feature bypass in n/a

> Remote attackers can evade HTTP traffic detection in 3Com TippingPoint IPS by exploiting improper handling of Unicode character encodings.

- **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:** 16 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8h4q-hf82-q8rj

## What is CVE-2007-2734?

CVE-2007-2734 is a high-severity vulnerability in n/a, published on 16 May 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 3Com TippingPoint IPS do not properly handle certain full-width and half-width Unicode character encodings in an HTTP POST request, which might allow remote attackers to evade detection of HTTP traffic.

## Which versions are affected by CVE-2007-2734?

It affects 8 products.


Products: 3com 3crtpx505-73, 3com 3crx506-96, 3com Tippingpoint 200, 3com Tippingpoint 200e, 3com Tippingpoint 2400e, 3com Tippingpoint 50, 3com Tippingpoint 5000e, 3com Tippingpoint 600e.

## How do I fix CVE-2007-2734?

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

## Is CVE-2007-2734 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2734 and fix it if it is affected.

What it is: CVE-2007-2734 is a high-severity vulnerability in n/a, published on 16 May 2007. 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-2007-2734 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-2007-2734/ (Markdown: https://insights.sbomify.com/CVE-2007-2734/index.md)
```

## Sources

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

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