-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WS-2018-0629 (Critical) detected in woodstox-core-5.0.2.jar #26
Comments
✔️ 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. |
ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory. |
✔️ 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. |
ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory. |
WS-2018-0629 - Critical Severity Vulnerability
Vulnerable Library - woodstox-core-5.0.2.jar
Woodstox is a high-performance XML processor that implements Stax (JSR-173), SAX2 and Stax2 APIs
Library home page: http://fasterxml.com
Path to dependency file: /vc-worker/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.2/woodstox-core-5.0.2.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.2/woodstox-core-5.0.2.jar
Dependency Hierarchy:
Found in HEAD commit: dd01a1d4381c7a3b94ba25748c015a094c33088e
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
Release Date: 2018-08-23
Fix Resolution: 5.3.0
⛑️ Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: