Homepage

org.apache.camel:camel-knative-http@4.3.0

  • latest version

    4.23.0

  • latest non vulnerable version

    4.23.0

  • first published

    4 years ago

  • latest version published

    11 days 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.apache.camel:camel-knative-http 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 via the KnativeHttpConsumer in the camel-knative HTTP consumer. An external sender can trigger a consumer-side route failure by sending a request that causes exchange processing to fail, then read the exception class, message, and stack trace returned in the HTTP response. This exposes deployment details such as route structure, host or filesystem names, and, when exception messages contain them, configuration or connection strings directly.

    Workarounds

    • Add an onException handler that explicitly sets the response body, preventing the Knative HTTP consumer from returning exception details to callers.

    How to fix Information Exposure?

    Upgrade org.apache.camel:camel-knative-http to version 4.18.5, 4.22.1 or higher.

    [4.0.0,4.18.5)[4.19.0,4.22.1)
    • H
    Improper Certificate Validation

    Affected versions of this package are vulnerable to Improper Certificate Validation via the configureOptions() method in the Knative HTTP client. An attacker on the network path can impersonate the server and read TLS traffic by intercepting connections when SSL is enabled without a truststore or trusted-certificate path, because the client accepts every presented certificate; KnativeOidcClientOptions inherits this behavior.

    Workarounds

    • Configure a truststore explicitly wherever SSL is enabled on the Knative HTTP client to ensure the server certificate is validated and prevent an attacker on the network path from impersonating the server.

    How to fix Improper Certificate Validation?

    Upgrade org.apache.camel:camel-knative-http to version 4.18.5, 4.22.1 or higher.

    [4.0.0,4.18.5)[4.19.0,4.22.1)
    Go back to all versions of this package