search

samjcs / log4shell-possible-malware

Repo I found while it was in proccess of being deleted that could contain malware using the log4j exploit
0 stars 0 forks source link

CVE-2021-33037 (Medium) detected in tomcat-embed-core-8.5.58.jar #9

Open mend-for-github-com[bot] opened 2 years ago

mend-for-github-com[bot] commented 2 years ago

CVE-2021-33037 - Medium Severity Vulnerability

Vulnerable Library - tomcat-embed-core-8.5.58.jar

Core Tomcat implementation

Path to dependency file: /pom.xml

Path to vulnerable library: /pache/tomcat/embed/tomcat-embed-core/8.5.58/tomcat-embed-core-8.5.58.jar

Dependency Hierarchy: - :x: **tomcat-embed-core-8.5.58.jar** (Vulnerable Library)

Found in HEAD commit: 8e3a1e1b8d8f62ed86ec27f3a50f080a66037011

Found in base branch: main

Vulnerability Details

Apache Tomcat 10.0.0-M1 to 10.0.6, 9.0.0.M1 to 9.0.46 and 8.5.0 to 8.5.66 did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: - Tomcat incorrectly ignored the transfer encoding header if the client declared it would only accept an HTTP/1.0 response; - Tomcat honoured the identify encoding; and - Tomcat did not ensure that, if present, the chunked encoding was the final encoding.

Publish Date: 2021-07-12

URL: CVE-2021-33037

CVSS 3 Score Details (5.3)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://lists.apache.org/thread.html/rd84fae1f474597bdf358f5bdc0a5c453c507bd527b83e8be6b5ea3f4%40%3Cannounce.tomcat.apache.org%3E

Release Date: 2021-07-12

Fix Resolution: 8.5.68

mend-for-github-com[bot] commented 2 years ago

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

mend-for-github-com[bot] commented 2 years ago

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