Homepage

org.apache.camel:camel-as2-api@4.10.0

  • latest version

    4.23.0

  • latest non vulnerable version

    4.23.0

  • first published

    8 years ago

  • latest version published

    12 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-as2-api 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
    • H
    Exposure of Data Element to Wrong Session

    Affected versions of this package are vulnerable to Exposure of Data Element to Wrong Session via the ResponseMDN handler in the AS2 component. In a deployment serving multiple trading partners with dynamic per-request keys, ordinary concurrent or successive AS2 requests can cause ResponseMDN to reuse signing material loaded from another request’s HttpContext, so an MDN for one partner’s exchange is signed with another partner’s private key. This misattributes the receipt and uses one partner’s signing material for another partner’s exchange; it does not disclose the private key.

    Workarounds

    • Run a separate Camel context for each trading partner to prevent signing material from being shared across partners.

    How to fix Exposure of Data Element to Wrong Session?

    Upgrade org.apache.camel:camel-as2-api to version 4.18.5, 4.22.1 or higher.

    [4.0.0,4.18.5)[4.19.0,4.22.1)
    • H
    Server-side Request Forgery (SSRF)

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the asynchronous MDN delivery process in the camel-as2 component. An attacker can make the AS2 receiver connect to attacker-chosen or internally reachable hosts by sending a message with a malicious Receipt-Delivery-Option header; if MDN credentials are configured, the receiver also sends them to the chosen host.

    Workarounds

    • Restrict outbound connectivity from the AS2 receiver to partner endpoints that legitimately receive MDNs, preventing sender-supplied destinations from reaching other hosts.
    • Do not attach MDN-delivery credentials that are valid for hosts other than those authorized partner endpoints, limiting credential exposure to an attacker-chosen destination.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade org.apache.camel:camel-as2-api 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