# CVE-2005-3747: Mortbay Jetty Discloses JSP Source Code

> Remote attackers can obtain source code of JSP pages in Jetty web server by exploiting URL-encoded backslash characters in requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cwq3-qp8v-w8q3

## What is CVE-2005-3747?

CVE-2005-3747 is a medium-severity vulnerability in n/a, published on 22 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in Jetty before 5.1.6 allows remote attackers to obtain source code of JSP pages, possibly involving requests for .jsp files with URL-encoded backslash ("%5C") characters.  NOTE: this might be the same issue as CVE-2006-2758.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2005-3747?

2 open source packages ship an affected version, including org.mortbay.jetty:jetty. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.mortbay.jetty:jetty` | Maven | All versions | 5.1.6 |
| `org.mortbay.jetty:jetty` | Maven | All versions | 5.1.6 |

Products: Mortbay Jetty.

## How do I fix CVE-2005-3747?

Upgrade org.mortbay.jetty:jetty to 5.1.6 or later.

## Is CVE-2005-3747 being exploited?

There is no known exploitation of CVE-2005-3747 in the wild and no public exploit code.

Public exploit code:

- promise webpam 2.2.0.13 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-4611](https://insights.sbomify.com/CVE-2009-4611/): Improper input validation in Mort Bay Jetty (high 7.5)
- [CVE-2009-5048](https://insights.sbomify.com/CVE-2009-5048/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2011-4461](https://insights.sbomify.com/CVE-2011-4461/): Improper Input Validation in Jetty (medium 5.3)
- [CVE-2009-4609](https://insights.sbomify.com/CVE-2009-4609/): Information disclosure in n/a (medium 5.0)
- [CVE-2009-1523](https://insights.sbomify.com/CVE-2009-1523/): Directory traversal in Mort Bay Jetty (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3747 and fix it if it is affected.

What it is: CVE-2005-3747 is a medium-severity vulnerability in n/a, published on 22 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3747 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.mortbay.jetty:jetty (Maven): affected all versions; fixed in 5.1.6
- org.mortbay.jetty:jetty (Maven): affected all versions; fixed in 5.1.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-3747/ (Markdown: https://insights.sbomify.com/CVE-2005-3747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-3747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-3747
- OSV: https://osv.dev/vulnerability/CVE-2005-3747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-3747/
Summaries are generated and may contain mistakes; the official description above is the record.