dbcve.org
SecurityreporterApplication · Securecomputing

CVE-2007-4043

CRITICAL · 9.8 CVSS v3.1 Published 2007-07-27
Fix available
A fix is available. Upgrade to after 4.6.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authentication bypass vulnerability in file.cgi of Secure Computing SecurityReporter (Network Security Analyzer) allows remote attackers to bypass authentication via a name parameter ending with '%00.gif' sequence. Additionally, a separate path traversal vulnerability enables attackers to download arbitrary files from the system.

MitigationUpgrade to SecurityReporter version 4.6.3 or later to address both the authentication bypass and path traversal vulnerabilities. Implement network-level access controls as a temporary measure if immediate upgrade is not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SecurityreporterApplication
Affected:<= 4.6.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SecurityReporter is installed
    Check for the SecurityReporter web application by looking for its web interface, typically on common HTTP/HTTPS ports. Look for files related to 'SecurityReporter' or 'file.cgi' in the web server's document root or CGI directories.
    Affected if The SecurityReporter (Network Security Analyzer) web application is present and accessible on the network.
  2. Determine the installed version
    Access the SecurityReporter web interface and look for version information, typically found in an 'About' page, help section, or in the HTML source. Alternatively, check configuration files or the software installation directory for version markers.
    Affected if The installed version is 4.6.3 or lower.
  3. Verify file.cgi is accessible
    Attempt to access the file.cgi script via HTTP/HTTPS request to the SecurityReporter web path, for example: GET /cgi-bin/file.cgi
    Affected if The file.cgi script returns a response (either an error page or authentication prompt), indicating it is accessible.
  4. Test for authentication bypass
    Send a request to file.cgi with a name parameter ending in '%00.gif', for example: GET /cgi-bin/file.cgi?name=test%00.gif
    Affected if The response bypasses authentication and returns content that would normally require login, or grants unauthorized access to the application.
  5. Test for path traversal vulnerability
    Send a request to file.cgi with path traversal sequences, for example: GET /cgi-bin/file.cgi?file=../../../../etc/passwd or similar traversal patterns pointing to system files.
    Affected if The application returns contents of files outside the intended directory, confirming path traversal is possible.

The environment is affected if SecurityReporter version 4.6.3 or lower is installed and the file.cgi script is accessible, allowing either authentication bypass via '%00.gif' suffix or unauthorized file access via path traversal.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 4.6.3
Interim mitigation

Upgrade to SecurityReporter version 4.6.3 or later to address both the authentication bypass and path traversal vulnerabilities. Implement network-level access controls as a temporary measure if immediate upgrade is not feasible.

Recommended fix High confidence

SecurityReporter 4.6.3 or later

  1. 1. Verify current SecurityReporter version by checking the application interface or documentation
  2. 2. Obtain SecurityReporter version 4.6.3 or later from the official vendor (Secure Computing/Next Generation Security)
  3. 3. Review upgrade documentation and any migration guides provided by the vendor
  4. 4. Perform a backup of the current configuration and database
  5. 5. Stop the SecurityReporter service
  6. 6. Install version 4.6.3 or later following vendor installation procedures
  7. 7. Restart the service and verify the application is functioning correctly
  8. 8. Confirm the file.cgi authentication bypass is no longer exploitable

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Securityreporter Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-4043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-4043 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data