org.springframework:spring-messaging@4.1.5.RELEASE vulnerabilities

  • latest version

    6.2.1

  • latest non vulnerable version

  • first published

    11 years ago

  • latest version published

    11 days ago

  • licenses detected

  • package manager

  • Direct Vulnerabilities

    Known vulnerabilities in the org.springframework:spring-messaging package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Denial of Service (DoS)

    org.springframework:spring-messaging is a framework and inversion of control container for the Java platform.

    Affected versions of this package are vulnerable to Denial of Service (DoS) when the application is used with a STOMP over WebSocket endpoint.

    How to fix Denial of Service (DoS)?

    Upgrade org.springframework:spring-messaging to version 5.2.22.RELEASE, 5.3.20 or higher.

    [,5.2.22.RELEASE)[5.3.0,5.3.20)
    • C
    Arbitrary Code Execution

    org.springframework:spring-messaging is a framework and inversion of control container for the Java platform.

    Affected versions of this package are vulnerable to Arbitrary Code Execution. It allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack. This CVE is due to incomplete fix for CVE-2018-1270

    How to fix Arbitrary Code Execution?

    Upgrade org.springframework:spring-messaging to version 4.3.16.RELEASE, 5.0.5.RELEASE or higher.

    [,4.3.16.RELEASE)[5.0.0.RELEASE,5.0.5.RELEASE)
    • C
    Arbitrary Code Execution

    org.springframework:spring-messaging is a framework and inversion of control container for the Java platform.

    Affected versions of this package are vulnerable to Arbitrary Code Execution. It allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.

    How to fix Arbitrary Code Execution?

    Upgrade org.springframework:spring-messaging to version 4.3.16.RELEASE, 5.0.5.RELEASE or higher.

    [,4.3.16.RELEASE)[5.0.0.RELEASE,5.0.5.RELEASE)