You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Path to dependency file: Resiliency-Studio/resiliency-studio-service/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar
ℹ️ This issue was automatically closed by WhiteSource because it is a duplicate of an existing issue: #53
mend-for-github-combot
changed the title
WS-2018-0629 (High) detected in woodstox-core-5.0.3.jar
WS-2018-0629 (High) detected in woodstox-core-5.0.3.jar - autoclosed
Nov 5, 2021
WS-2018-0629 - High Severity Vulnerability
Vulnerable Library - woodstox-core-5.0.3.jar
Woodstox is a high-performance XML processor that implements Stax (JSR-173), SAX2 and Stax2 APIs
Library home page: https://github.com/FasterXML/woodstox
Path to dependency file: Resiliency-Studio/resiliency-studio-service/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar
Dependency Hierarchy:
Found in HEAD commit: 27f5ba6623ed8d6b149733f3ad245fc8133f1ffc
Found in base branch: master
Vulnerability Details
The woodstox-core package is vulnerable to improper restriction of XXE reference.
Publish Date: 2018-08-23
URL: WS-2018-0629
CVSS 3 Score Details (9.1)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: FasterXML/woodstox#61
Release Date: 2018-08-23
Fix Resolution: com.fasterxml.woodstox:woodstox-core:5.3.0
The text was updated successfully, but these errors were encountered: