org.apache.storm:storm-client@2.2.0

  • latest version

    2.8.6

  • first published

    7 years ago

  • latest version published

    25 days ago

  • licenses detected

  • package registry

  • Direct Vulnerabilities

    Known vulnerabilities in the org.apache.storm:storm-client 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
    Missing Authentication for Critical Function

    Affected versions of this package are vulnerable to Missing Authentication for Critical Function via the TlsTransportPlugin. An attacker can gain unauthorized access by establishing a TLS connection without presenting a valid client certificate, as the system assigns an anonymous principal and does not reject the connection.

    Note: This is only exploitable if client certificate authentication is not required and authorization rules do not explicitly deny access to CN=ANONYMOUS.

    How to fix Missing Authentication for Critical Function?

    Upgrade org.apache.storm:storm-client to version 2.8.7 or higher.

    [,2.8.7)
    • H
    Deserialization of Untrusted Data

    Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the TGT credential field via the Nimbus Thrift API, due to deserialization of base64-encoded data using ObjectInputStream.readObject() without class filtering or validation. A user with topology submission rights can achieve remote code execution by submitting a crafted serialized object as an authenticated user with topology submission rights.

    How to fix Deserialization of Untrusted Data?

    Upgrade org.apache.storm:storm-client to version 2.8.6 or higher.

    [,2.8.6)
    • L
    Exposure of Sensitive Information to an Unauthorized Actor

    Affected versions of this package are vulnerable to Exposure of Sensitive Information to an Unauthorized Actor via the File.createTempFile method. A local attacker can read sensitive information by accessing the temporary file created in the system's temporary directory.

    Note:

    This is only exploitable if 'java.io.tmpdir' system property is not explicitly set and 'ui.disable.spout.lag.monitoring' is set to false. Also, the impact is limited as the temporary file gets deleted soon after its creation.

    This vulnerability does not impact modern MacOS Operating Systems.

    How to fix Exposure of Sensitive Information to an Unauthorized Actor?

    Upgrade org.apache.storm:storm-client to version 2.6.0 or higher.

    [2.0.0,2.6.0)