Fix: Vulnerability for logback-classic #116
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Temporarily we can ignore canCommit() issue as the ServiceNow instance is intermittently going down, causing PR failures. This is a known intermittent issue and does not impact the functionality. |
sgarg-CS
assigned
vikasrathee-cs and
sgarg-CS and unassigned
vikasrathee-cs and
sgarg-CS
sgarg-CS
approved these changes
Aug 5, 2025
AbhishekKumar9984
force-pushed
the
moss-log-fix
branch
from
42ebd33 to
ab41eb5
Compare
vikasrathee-cs
approved these changes
Aug 6, 2025
minurajeeve
approved these changes
Aug 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
Resolved a high-severity Denial of Service (DoS) vulnerability (GHSA-vmq6-5m68-f53m) in the logback receiver component (ch.qos.logback:logback-classic). This vulnerability allowed attackers to exploit a serialization flaw by sending malicious data to the receiver component, potentially causing system unavailability. The issue is present in environments where the logback receiver component is deployed, specifically affecting logback-classic version 1.2.8.
Root Cause:
The logback receiver component failed to adequately validate serialized input data. If the receiver was enabled, attackers could send specially crafted serialized payloads that triggered resource exhaustion, leading to Denial of Service.
Fix : upgrading ch.qos.logback:logback-classic to a secure version 1.3.15 .
JIRA Ticket: https://cdap.atlassian.net/browse/PLUGIN-1907