Update dependency ch.qos.logback:logback-classic to v1.2.13 [SECURITY]#1048
Update dependency ch.qos.logback:logback-classic to v1.2.13 [SECURITY]#1048renovate[bot] wants to merge 1 commit into
Conversation
|
Renovate Jira issue ID: SLE-1494 |
Summary
This PR updates the logback-classic dependency in the test project from 1.1.7 to 1.2.13 to address CVE-2017-5929, a critical deserialization vulnerability in the SocketServer and ServerSocketReceiver components. The change is a single-file update affecting only the integration test project's pom.xml. Version 1.2.13 contains the fix for this vulnerability (introduced in 1.2.0) and is the latest stable release in the 1.2.x series. What reviewers should knowWhat to check:
No other files affected — this is a straightforward Renovate-generated dependency bump with minimal blast radius.
|
![sonar-review-alpha[bot]](https://avatars.githubusercontent.com/in/3025063?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
renovate
Bot
force-pushed
the
renovate/maven-ch.qos.logback-logback-classic-vulnerability
branch
from
bed45cd to
50f423c
Compare
|
This PR contains the following updates:
1.1.7→1.2.13Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
QOS.ch Logback vulnerable to Deserialization of Untrusted Data
CVE-2017-5929 / GHSA-vmfg-rjjm-rjrj
More information
Details
QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components. The RemoteStreamAppenderClient class in logback-classic and the SocketNode classes in logback-classic and logback-access allow data to be deserialized over a Java Socket, via an ObjectInputStream, without validating the data beforehand. When data is received from the Socket, to be logged, it is deserialized into Java objects.An attacker can exploit this vulnerability by sending malicious, serialized Java objects over the connection to the Socket, which may result in execution of arbitrary code when those objects are deserialized. Note that although logback-core is implicated by the Logback project here, the Sonatype Security Research team discovered that the vulnerability is actually present in the logback-classic and logback-access components. Versions prior to 1.2.0 are vulnerable, as stated in the advisory.
Severity
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
logback serialization vulnerability
CVE-2023-6378 / GHSA-vmq6-5m68-f53m
More information
Details
A serialization vulnerability in logback receiver component part of logback allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
This is only exploitable if logback receiver component is deployed. See https://logback.qos.ch/manual/receivers.html
Severity
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Configuration
📅 Schedule: (in timezone CET)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.