Search for packages
| purl | pkg:deb/debian/jetty9@9.2.25-1?distro=trixie |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-12gq-ezut-ckhz |
CVE-2017-7657
GHSA-vgg8-72f2-qm23 |
|
| VCID-kvqz-fppe-d7fe |
CVE-2017-7658
GHSA-6x9x-8qw9-9pp6 |
|
| VCID-u2b5-uyd6-fbh9 | In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system. |
CVE-2018-12536
GHSA-9rgv-h7x4-qw8g |
| VCID-znv6-77jf-v3gu | In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), HTTP/0.9 is handled poorly. An HTTP/1 style request line (i.e. method space URI space version) that declares a version of HTTP/0.9 was accepted and treated as a 0.9 request. If deployed behind an intermediary that also accepted and passed through the 0.9 version (but did not act on it), then the response sent could be interpreted by the intermediary as HTTP/1 headers. This could be used to poison the cache if the server allowed the origin client to generate arbitrary content in the response. |
CVE-2017-7656
GHSA-84q7-p226-4x5w |