TomcatWeb server / proxy · Apache
CVE-2005-0808
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 · uneditedApache Tomcat before 5.x allows remote attackers to cause a denial of service (application crash) via a crafted AJP12 packet to TCP port 8007.
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 · low confidenceApache Tomcat versions prior to 5.x contain a denial of service vulnerability where remote attackers can send a specially crafted AJP12 packet to TCP port 8007 (the Apache JServ Protocol connector port), causing the Tomcat application to crash.
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
TomcatWeb server / proxy
= 3.0= 3.1= 3.1.1= 3.2= 3.2.1= 3.2.2= 3.2.3= 3.2.4= 3.3= 3.3.1= 3.3.1aCVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Apache Tomcat is installedCheck for Tomcat installation directories (common paths: /opt/tomcat, /usr/share/tomcat, C:\Program Files\Apache Software Foundation\Tomcat) or look for running Java processes with 'tomcat' in the command lineAffected if Apache Tomcat is installed and running
-
Determine the Tomcat versionCheck the version number in release files such as RELEASE-NOTES, BUILD-INFO, or the VERSION file typically found in the Tomcat home directory, or examine the serverinfo.properties file in the lib directoryAffected if The installed version is any of: 3.0, 3.1, 3.1.1, 3.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3, 3.3.1, or 3.3.1a
-
Verify if AJP12 connector is configuredExamine the server.xml configuration file in the conf directory for an AJP12 connector definition pointing to port 8007. Look for entries like <Connector className="org.apache.ajp.tomcat4.Ajp13Connector" port="8007"Affected if An AJP12 or Ajp13 connector is explicitly configured on port 8007 in server.xml
-
Check if port 8007 is listeningUse netstat or ss commands to check if port 8007 is in LISTEN state: netstat -an | grep 8007 or ss -tlnp | grep 8007Affected if Port 8007 is open and accepting connections on any network interface
A user is affected if they are running any Tomcat version from 3.0 to 3.3.1a with the AJP12 connector enabled and port 8007 exposed on the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to Apache Tomcat 5.x or later. If immediate upgrade is not feasible, implement network segmentation to restrict unauthorized access to port 8007 from untrusted networks.
Fix this in Tomcat
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2005-0808 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2005-0808 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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