CVE-2007-5615
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 · uneditedCRLF injection vulnerability in Mortbay Jetty before 6.1.6rc0 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via unspecified vectors.
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 confidenceCRLF injection vulnerability in Mortbay Jetty versions prior to 6.1.6rc0 allows remote attackers to inject arbitrary HTTP headers by inserting carriage return and line feed (CRLF) sequences into input fields. This enables HTTP response splitting attacks where malicious headers or response bodies can be injected into server responses, potentially leading to cross-site scripting (XSS), cache poisoning, or session hijacking.
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<= 6.1.6rc0CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 version from JAR manifestLocate the jetty.jar or start.jar file in the Jetty installation directory and inspect its META-INF/MANIFEST.MF file for the Implementation-Version or Bundle-Version attributeAffected if The version listed is 6.1.6rc0 or earlier, or if no version is displayed and the installation dates to before late 2007
-
Check Jetty version from startup logsReview the console output or log files generated when Jetty starts, as the version is typically printed during startupAffected if The startup logs show a version of 6.1.6rc0 or earlier
-
Verify Jetty is the HTTP server in useRun a command such as 'netstat -an' or 'ss -tlnp' to list listening ports, then access the server via HTTP to observe default error pages or check for 'Jetty' in server response headersAffected if The server identifies itself as Mortbay Jetty or Eclipse Jetty version 6.x and the version is 6.1.6rc0 or earlier
-
Confirm the server handles user inputSubmit test requests with CRLF sequences (%0D%0A URL-encoded) in query parameters or form inputs to observe whether the server reflects these characters in its response headersAffected if The server returns the CRLF sequences unmodified in response headers, indicating the injection vulnerability is present
A user is affected if their Mortbay Jetty installation shows version 6.1.6rc0 or any earlier 6.x version, and the server processes user-supplied input that could be reflected in HTTP headers.
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 Mortbay Jetty to version 6.1.6rc0 or later. If upgrading is not feasible, implement input validation to reject requests containing CRLF sequences in user-supplied data.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5615 — 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-2007-5615 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