# CVE-2007-4043: Auth bypass in n/a

> Remote attackers can bypass authentication in Secure Computing SecurityReporter via a null byte injection in the name parameter, potentially accessing arbitrary files.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2007
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-gcc5-hrjv-52gx

## What is CVE-2007-4043?

CVE-2007-4043 is a critical authentication bypass vulnerability in n/a, published on 27 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

file.cgi in Secure Computing SecurityReporter (aka Network Security Analyzer) before 4.6.3 allows remote attackers to bypass authentication via a name parameter ending with a "%00.gif" sequence. NOTE: a separate traversal vulnerability could be leveraged to download arbitrary files.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Securecomputing Securityreporter.

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

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

## Is CVE-2007-4043 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-3985](https://insights.sbomify.com/CVE-2007-3985/): Path traversal in n/a (medium 5.0)
- [CVE-2007-3986](https://insights.sbomify.com/CVE-2007-3986/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4043 is a critical authentication bypass vulnerability in n/a, published on 27 Jul 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-4043 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-4043/ (Markdown: https://insights.sbomify.com/CVE-2007-4043/index.md)
```

## Sources

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

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