Homepage

ch.qos.logback:logback-core@1.3.0-beta0

  • latest version

    1.5.37

  • latest non vulnerable version

    1.5.37

  • first published

    19 years ago

  • latest version published

    9 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 ch.qos.logback:logback-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
    Deserialization of Untrusted Data

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to Deserialization of Untrusted Data in HardenedObjectInputStream, whose resolveClass allowlist admitted any class whose name starts with java.lang or java.util rather than matching specific authorized classes. An attacker can instantiate dangerous classes such as java.lang.ProcessBuilder during deserialization, reaching remote code execution through a gadget chain, by delivering a malicious serialized object to a logback component that deserializes it, such as its socket receiver for serialized logging events (SocketNode). Exploitation requires the application to deserialize attacker-controlled serialized data through logback, in practice via its socket-based receiver, together with a usable gadget class on the classpath.

    How to fix Deserialization of Untrusted Data?

    Upgrade ch.qos.logback:logback-core to version 1.5.33 or higher.

    [,1.5.33)
    • H
    Expression Injection

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to Expression Injection in the Janino-evaluated condition attribute of <if> configuration elements, handled by IfModelHandler, whose denylist blocked only the literal new operator. A user who can modify the logback configuration can execute arbitrary code by writing an <if> condition that evades that denylist, either through references it did not cover such as Runtime or springframework, or through Unicode escape sequences like \u that reconstruct the blocked new operator. Exploitation requires write access to the logback configuration and the use of conditional <if> processing with Janino present on the classpath.

    How to fix Expression Injection?

    Upgrade ch.qos.logback:logback-core to version 1.5.36 or higher.

    [0.9.20,1.5.36)
    • L
    External Initialization of Trusted Variables or Data Stores

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to External Initialization of Trusted Variables or Data Stores during the configuration file processing. An attacker can instantiate arbitrary classes already present on the class path by compromising an existing configuration file.

    How to fix External Initialization of Trusted Variables or Data Stores?

    Upgrade ch.qos.logback:logback-core to version 1.5.25 or higher.

    [0.9.20,1.5.25)
    • M
    External Initialization of Trusted Variables or Data Stores

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to External Initialization of Trusted Variables or Data Stores via the conditional processing of the logback.xml configuration file when both the Janino library and Spring Framework are present on the class path. An attacker can execute arbitrary code by compromising an existing configuration file or injecting a malicious environment variable before program execution. This is only exploitable if the attacker has write access to a configuration file or can set a malicious environment variable.

    How to fix External Initialization of Trusted Variables or Data Stores?

    Upgrade ch.qos.logback:logback-core to version 1.3.16, 1.5.19 or higher.

    [,1.3.16)[1.4.0,1.5.19)
    • M
    Improper Neutralization of Special Elements

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to Improper Neutralization of Special Elements via the JaninoEventEvaluator extension. An attacker can execute arbitrary code by compromising an existing logback configuration file or injecting an environment variable before program execution.

    How to fix Improper Neutralization of Special Elements?

    Upgrade ch.qos.logback:logback-core to version 1.3.15, 1.5.13 or higher.

    [,1.3.15)[1.4.0,1.5.13)
    • L
    Server-side Request Forgery (SSRF)

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) through the SaxEventRecorder process. An attacker can forge requests by compromising logback configuration files in XML.

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

    Upgrade ch.qos.logback:logback-core to version 1.3.15, 1.5.13 or higher.

    [,1.3.15)[1.4.0,1.5.13)
    • H
    Denial of Service (DoS)

    ch.qos.logback:logback-core is a logback-core module.

    Affected versions of this package are vulnerable to Denial of Service (DoS). An attacker can mount a denial-of-service attack by sending poisoned data. This is only exploitable if logback receiver component is deployed.

    How to fix Denial of Service (DoS)?

    Upgrade ch.qos.logback:logback-core to version 1.2.13, 1.3.12, 1.4.12 or higher.

    [,1.2.13)[1.3.0-alpha0,1.3.12)[1.4.0,1.4.12)
    Go back to all versions of this package