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

> Remote attackers can bypass ModSecurity request rules by sending POST data with null bytes, exploiting parser differences.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 8 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j86f-xc6j-vf9f

## What is CVE-2007-1359?

CVE-2007-1359 is a medium-severity vulnerability in n/a, published on 8 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Interpretation conflict in ModSecurity (mod_security) 2.1.0 and earlier allows remote attackers to bypass request rules via application/x-www-form-urlencoded POST data that contains an ASCIIZ (0x00) byte, which mod_security treats as a terminator even though it is still processed as normal data by some HTTP parsers including PHP 5.2.0, and possibly parsers in Perl, and Python.

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

It affects 1 product.


Products: Mod Security Mod Security.

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

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

## Is CVE-2007-1359 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1359 exists.

Public exploit code:

- mod_security 2.1.0 - ASCIIZ byte POST Rules Bypass (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1171](https://insights.sbomify.com/CVE-2003-1171/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1765](https://insights.sbomify.com/CVE-2004-1765/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1359 is a medium-severity vulnerability in n/a, published on 8 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1359 exists.

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-1359/ (Markdown: https://insights.sbomify.com/CVE-2007-1359/index.md)
```

## Sources

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

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