# CVE-2010-1329: Security feature bypass in n/a

> Remote attackers can bypass intrusion-prevention functionality in Imperva SecureSphere firewalls by sending requests with appended long strings.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:C/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:** 15 Apr 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f243-jmp3-fr46

## What is CVE-2010-1329?

CVE-2010-1329 is a high-severity vulnerability in n/a, published on 15 Apr 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Imperva SecureSphere Web Application Firewall and Database Firewall 5.0.0.5082 through 7.0.0.7078 allow remote attackers to bypass intrusion-prevention functionality via a request that has an appended long string containing an unspecified manipulation.

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

It affects 2 products.


Products: Imperva Securesphere Database Firewall, Imperva Securesphere Web Application Firewall.

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

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

## Is CVE-2010-1329 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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