Information Exposure Affecting jetty-monitor package, versions *


Severity

Recommended
0.0
low
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.34% (73rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Information Exposure vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS7-JETTYMONITOR-1991109
  • published26 Jul 2021
  • disclosed27 Jun 2018

Introduced: 27 Jun 2018

CVE-2018-12536  (opens in a new tab)
CWE-209  (opens in a new tab)

How to fix?

There is no fixed version for Centos:7 jetty-monitor.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jetty-monitor package and not the jetty-monitor package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1