org.http4k:http4k-core@6.39.0.0

  • latest version

    6.56.0.0

  • latest non vulnerable version

  • first published

    9 years ago

  • latest version published

    4 days ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the org.http4k:http4k-core 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
    Information Exposure

    Affected versions of this package are vulnerable to Information Exposure in the BasicCookieStorage process, which does not enforce proper scoping rules for cookies as specified in RFC 6265. An attacker can access or receive cookies intended for other domains or schemes by leveraging a single storage instance across multiple origins or by sending Secure cookies over plain HTTP. This is only exploitable if a client uses the same storage instance for multiple origins or schemes.

    How to fix Information Exposure?

    Upgrade org.http4k:http4k-core to version 4.51.0.0, 5.42.0.0, 6.48.0.0 or higher.

    [,4.51.0.0)[5.0.0.0,5.42.0.0)[6.0.0.0,6.48.0.0)
    • M
    HTTP Request Smuggling

    Affected versions of this package are vulnerable to HTTP Request Smuggling in the reverseProxy process. An attacker can bypass routing-based authorization by sending a specially crafted Host header that matches a configured virtual host via substring, allowing unauthorized access to restricted routes. This is only exploitable if the deployment uses reverseProxy() or reverseProxyRouting() as a public-facing inbound HTTP handler with two or more configured virtual hosts.

    How to fix HTTP Request Smuggling?

    Upgrade org.http4k:http4k-core to version 4.51.0.0, 5.42.0.0, 6.49.0.0 or higher.

    [,4.51.0.0)[5.0.0.0,5.42.0.0)[6.0.0.0,6.49.0.0)
    • H
    Insufficient Verification of Data Authenticity

    Affected versions of this package are vulnerable to Insufficient Verification of Data Authenticity through the misleadingly named HmacSha256.hash function. An attacker can bypass message authentication by exploiting the use of an unkeyed digest where a keyed HMAC was expected. This is only exploitable if downstream callers incorrectly assume HmacSha256.hash provides keyed authentication and use it for message authentication purposes.

    How to fix Insufficient Verification of Data Authenticity?

    Upgrade org.http4k:http4k-core to version 6.49.0.0 or higher.

    [,6.49.0.0)