Debian LinuxOperating system · Debian
CVE-2009-5046
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 · uneditedJSP Dump and Session Dump Servlet XSS 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 confidenceCross-Site Scripting (XSS) vulnerability in the JSP Dump and Session Dump Servlet components of the Jetty web server versions prior to 6.1.22. The vulnerability allows attackers to inject malicious scripts through unsanitized input in these debugging servlets.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 versionRun 'java -jar jetty.jar --version' or check the jetty-version.xml file in the Jetty distribution, or look for version info in /usr/share/jetty/ on Debian systemsAffected if The detected version is earlier than 6.1.22
-
Locate JSP Dump and Session Dump Servlet classesSearch for 'jsp' and 'session' dump servlet classes in the Jetty lib or webapps directory, or check for files named similar to 'dump.jsp' or 'session.jsp' in deployed web applicationsAffected if These debug servlets are present in the Jetty deployment
-
Check web.xml for servlet mappingsExamine the web.xml configuration files in the etc/ directory or in individual webapp WEB-INF folders for servlet mappings to '/jsp/dump/*' or '/session/dump/*' or similar debug pathsAffected if Mappings to JSP Dump or Session Dump servlets are defined in active configuration files
-
Verify if debug servlets are accessibleAttempt to access http://localhost:8080/jsp/dump/ or http://localhost:8080/session/dump/ (adjust port as needed) to see if these debug endpoints respondAffected if The debug servlets are accessible and respond to requests
-
Check Debian Jetty package versionOn Debian systems, run 'dpkg -l | grep jetty' or 'apt-cache policy jetty' to determine the installed package versionAffected if The installed Jetty package version is earlier than 6.1.22-2+deb6u1 or similar fix version
Your environment is affected if you are running any Jetty version earlier than 6.1.22 with the JSP Dump or Session Dump servlets enabled and accessible.
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. If upgrading is not immediately possible, disable or remove the JSP Dump and Session Dump Servlets as a temporary workaround.
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-5046 — 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-5046 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