How severe is CVE-2005-3747?

No CVSS score has been assigned to CVE-2005-3747 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2005-3747?

CVE-2005-3747 affects the following packages: org.mortbay.jetty:jetty (Maven). Ecosystems affected: Maven.

How do I fix CVE-2005-3747?

Update org.mortbay.jetty:jetty to 5.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2005-3747 is resolved across your whole dependency graph.

How do I detect CVE-2005-3747 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mortbay.jetty:jetty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2005-3747 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2005-3747 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2005-3747, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2005-3747?

CVE-2005-3747 has an EPSS (Exploit Prediction Scoring System) score of 4.4%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2005-3747?

CVE-2005-3747 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2005-3747 published, and has it been updated?

CVE-2005-3747 was published on May 1, 2022 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2005-3747 — jetty

CVE-2005-3747 is a Information Exposure vulnerability in org.mortbay.jetty:jetty. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.mortbay.jetty:jetty — see the affected versions and patch details below.

Mortbay Jetty Discloses JSP Source Code

Published

May 1, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.mortbay.jetty:jetty

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.mortbay.jetty:jetty`	all versions	5.1.6`org.mortbay.jetty:jetty:5.1.6`

Affected Products

1 product · 240 configurations

Application

jettymortbay

≤ 5.1.5

163 versions

1.01.0.11.11.1.11.2.01.3.01.3.11.3.21.3.31.3.41.3.52.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-18571webappsphp

promise webpam 2.2.0.13 - Multiple Vulnerabilities

by LiquidWorm · Mar 7, 2012

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.mortbay.jetty:jetty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.mortbay.jetty:jetty to 5.1.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2005-3747 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2005-3747 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works