Summary
Installation information leak in Eclipse Jetty
In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.
Impact
CVE-2019-10247 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.eclipse.jetty:jetty-server to 9.2.28.v20190418 or later; org.eclipse.jetty:jetty-server to 9.3.27.v20190418 or later; org.eclipse.jetty:jetty-server to 9.4.17.v20190418 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2019-10247? CVE-2019-10247 is a medium-severity security vulnerability in org.eclipse.jetty:jetty-server (maven), affecting versions >= 7.0.0, <= 9.2.27.v20190403. It is fixed in 9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418.
- How severe is CVE-2019-10247? CVE-2019-10247 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.eclipse.jetty:jetty-server are affected by CVE-2019-10247? org.eclipse.jetty:jetty-server (maven) versions >= 7.0.0, <= 9.2.27.v20190403 is affected.
- Is there a fix for CVE-2019-10247? Yes. CVE-2019-10247 is fixed in 9.2.28.v20190418, 9.3.27.v20190418, 9.4.17.v20190418. Upgrade to this version or later.
- Is CVE-2019-10247 exploitable, and should I be worried? Whether CVE-2019-10247 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2019-10247 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2019-10247?
- Upgrade
org.eclipse.jetty:jetty-serverto 9.2.28.v20190418 or later - Upgrade
org.eclipse.jetty:jetty-serverto 9.3.27.v20190418 or later - Upgrade
org.eclipse.jetty:jetty-serverto 9.4.17.v20190418 or later
- Upgrade