Debian LinuxOperating system · Debian
CVE-2009-5045
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 · uneditedDump Servlet information leak in jetty before 6.1.22.
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 confidenceThe Jetty web server's Dump Servlet (a debugging feature) allows unauthenticated remote attackers to obtain sensitive server configuration, memory contents, thread states, and other internal runtime information in versions before 6.1.22, enabling reconnaissance for further attacks.
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
Debian LinuxOperating system
= 8.0< 6.1.22CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Jetty installation and versionLocate the Jetty jar files (typically in /usr/share/jetty, /opt/jetty, or the application lib directory) and check the jetty.jar version. Run: find / -name 'jetty*.jar' 2>/dev/null and examine the jar file properties, or check version files if present.Affected if The installed Jetty version is below 6.1.22 (e.g., 6.1.21, 6.1.20, etc.)
-
Verify the Dump Servlet is deployedCheck for the presence of the dump servlet in the web.xml deployment descriptor or look for the class file org/mortbay/servlet/DumpServlet in the Jetty lib or webapp directories. Also check if a web.xml maps /dump or /debug/dump URLs to this servlet.Affected if The Dump Servlet class is present in the deployment and mapped to a URL accessible over the network
-
Confirm network accessibility of the Dump ServletAttempt to access http://localhost:8080/dump or http://localhost:8080/debug/dump (adjust port as needed) using curl or a browser without authentication. Check the server response for detailed internal information.Affected if The Dump Servlet responds with configuration, memory, or thread information without requiring authentication
-
Check for Debian Jetty packageOn Debian systems, run: dpkg -l | grep jetty or apt-cache policy jetty to identify the installed package version.Affected if Running Debian 8.0 with the default Jetty package and the version is below 6.1.22
You are affected if your Jetty version is below 6.1.22 AND the Dump Servlet is deployed and accessible without authentication.
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 data6.1.22
Upgrade Jetty to version 6.1.22 or later, or disable/remove the Dump Servlet if not required in production environments.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-5045 — 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-2009-5045 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