search

billmcchesney1 / flowgate

Facility systems integrate with IT stack in data centers
Other
0 stars 0 forks source link

CVE-2023-6378 (High) detected in logback-classic-1.1.11.jar #348

Open mend-for-github-com[bot] opened 9 months ago

mend-for-github-com[bot] commented 9 months ago

CVE-2023-6378 - High Severity Vulnerability

Vulnerable Library - logback-classic-1.1.11.jar

logback-classic module

Library home page: http://logback.qos.ch

Path to dependency file: /operation-expert/pom.xml

Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.1.11/logback-classic-1.1.11.jar

Dependency Hierarchy: - spring-boot-starter-data-mongodb-1.4.7.RELEASE.jar (Root Library) - spring-boot-starter-1.4.7.RELEASE.jar - spring-boot-starter-logging-1.4.7.RELEASE.jar - :x: **logback-classic-1.1.11.jar** (Vulnerable Library)

Found in HEAD commit: dd01a1d4381c7a3b94ba25748c015a094c33088e

Found in base branch: master

Vulnerability Details

A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.

Publish Date: 2023-11-29

URL: CVE-2023-6378

CVSS 3 Score Details (7.1)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://logback.qos.ch/news.html#1.3.12

Release Date: 2023-11-29

Fix Resolution (ch.qos.logback:logback-classic): 1.2.13

Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-mongodb): 3.0.0

:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.

mend-for-github-com[bot] commented 3 months ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

mend-for-github-com[bot] commented 1 month ago

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.