Homepage

org.eclipse.jetty:jetty-server@9.4.58.v20250814

  • latest version

    12.1.11

  • latest non vulnerable version

    12.1.11

  • first published

    17 years ago

  • latest version published

    1 months ago

  • licenses detected

  • package registry

    View on Maven Central Repository
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the org.eclipse.jetty:jetty-server package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Improper Validation of Consistency within Input

    org.eclipse.jetty:jetty-server is a lightweight highly scalable java based web server and servlet engine.

    Affected versions of this package are vulnerable to Improper Validation of Consistency within Input through ComplianceUtils.verify(HttpURI, HttpFields, HttpCompliance, ComplianceViolation.Listener) in jetty-core/jetty-http/src/main/java/org/eclipse/jetty/http/ComplianceUtils.java. An attacker can bypass host consistency checks by sending a request whose :authority pseudo-header and Host header name different hosts, causing Jetty to accept the request and expose conflicting host identities to different code paths. This lets attacker-controlled host information survive inside the request, so logic that relies on Request.getServerName() or the URI authority can see one host while code reading the raw Host header sees another. In deployments that use host-based routing, ACLs, redirects, or tenant isolation, this can lead to incorrect request handling, host-based access control bypass, and attacker-influenced URL generation or logging.

    Notes

    • HTTP/1.1 already had its own authority/Host consistency path in HttpConnection/HttpChannelState; the gap was in the HTTP/2 and HTTP/3 server entry flow where the shared compliance check was invoked before that comparison happened.
    • The mismatch check only rejects when both values are present and differ after normalizing case and default ports, so requests with only one of :authority or Host present are not part of this issue.

    How to fix Improper Validation of Consistency within Input?

    Upgrade org.eclipse.jetty:jetty-server to version 9.4.61, 10.0.29, 11.0.29, 12.0.35, 12.1.9 or higher.

    [9.4.0,9.4.61)[10.0.0,10.0.29)[11.0.0,11.0.29)[12.0.0,12.0.35)[12.1.0,12.1.9)
    • M
    Interpretation Conflict

    org.eclipse.jetty:jetty-server is a lightweight highly scalable java based web server and servlet engine.

    Affected versions of this package are vulnerable to Interpretation Conflict due to inconsistent handling of invalid or unusual URIs in the parse() function on HttpURI.java‎. An attacker can bypass security controls or access restricted resources by crafting specially formatted URIs that are interpreted differently by various system components.

    How to fix Interpretation Conflict?

    Upgrade org.eclipse.jetty:jetty-server to version 12.0.31, 12.1.5 or higher.

    [9.4.0.M0,12.0.31)[12.1.0.alpha0,12.1.5)
    Go back to all versions of this package