dbcve.org
HTTP ServerWeb server / proxy · Apache

CVE-2003-0789

HIGH · 10.0 CVSS v2.0 Published 2003-11-03
Fix available
A fix is available. Upgrade to 2.0.48 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
mod_cgid in Apache before 2.0.48, when using a threaded MPM, does not properly handle CGI redirect paths, which could cause Apache to send the output of a CGI program to the wrong client.

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 · moderate confidence

mod_cgid in Apache versions prior to 2.0.48 contains a flaw when running with a threaded MPM where CGI redirect paths are improperly handled, potentially causing Apache to route the output of a CGI program to an incorrect client session.

MitigationUpgrade Apache to version 2.0.48 or later, or switch from a threaded MPM to a prefork MPM to eliminate the race condition.

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
HTTP ServerWeb server / proxy
Affected:>= 2.0.35, < 2.0.48

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Check Apache version
    Run 'apache2 -v' or 'httpd -v' to display the server version. For Apache 2.0.x, also check the version.h file or use 'apache2ctl -V'.
    Affected if The installed version is 2.0.35, 2.0.36, 2.0.37, 2.0.38, 2.0.39, 2.0.40, 2.0.41, 2.0.42, 2.0.43, 2.0.44, 2.0.45, 2.0.46, or 2.0.47.
  2. Identify the MPM in use
    Run 'apache2ctl -l' or 'httpd -l' to list compiled-in modules. Look for worker.c or winnt.c (threaded MPMs) versus prefork.c (prefork MPM). Alternatively, check the configuration file for 'LoadModule mpm_worker_module' or 'LoadModule mpm_prefork_module' directives.
    Affected if The server is using a threaded MPM such as worker (Unix) or winnt (Windows) rather than prefork.
  3. Confirm mod_cgid is loaded
    Check if mod_cgid is present in the compiled module list ('apache2ctl -l') or loaded via configuration ('LoadModule cgid_module modules/mod_cgid.so'). For Apache 2.0, verify the module exists in the modules directory.
    Affected if mod_cgid is loaded and active.
  4. Determine if CGI is enabled and in use
    Check for CGI script handlers in the Apache configuration (httpd.conf or included files). Look for 'ScriptAlias' directives, 'AddHandler cgi-script', or 'Options +ExecCGI' on directories containing CGI scripts.
    Affected if CGI scripts are enabled and the server is configured to execute them.

The environment is affected if Apache version is between 2.0.35 and 2.0.47 inclusive, combined with a threaded MPM (worker) and active CGI functionality via mod_cgid.

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 2.0.48 or later
Fixed in 2.0.48
Interim mitigation

Upgrade Apache to version 2.0.48 or later, or switch from a threaded MPM to a prefork MPM to eliminate the race condition.

Recommended fix High confidence

Apache HTTP Server 2.0.48 or later

  1. 1. Check the current Apache version: 'httpd -v' or 'apache2 -v'
  2. 2. Stop the Apache service: 'service httpd stop' or 'service apache2 stop'
  3. 3. Download Apache HTTP Server version 2.0.48 or later from a trusted mirror (e.g., archive.apache.org)
  4. 4. Extract and compile the new version with './configure', 'make', 'make install'
  5. 5. Verify the installation: 'httpd -v' to confirm version 2.0.48 or higher
  6. 6. Start the Apache service: 'service httpd start' or 'service apache2 start'
  7. 7. Test that CGI scripts function correctly and the mod_cgid module loads properly
  8. 8. If using a threaded MPM (such as worker or beos), verify CGI output is being sent to the correct client
Caveat Apache 2.0.x is an older branch; ensure compatibility with any custom modules or configurations before upgrading

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2003-0789 — 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-2003-0789 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