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 vulnerable library: /home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar
An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands with the same privileges as the account running the Servlet container. This applies to applications that allow untrusted users to upload/modify velocity templates running Apache Velocity Engine versions up to 2.2.
dev-mend-for-github-combot
changed the title
velocity-1.7.jar: 1 vulnerabilities (highest severity is: 8.8)
velocity-1.7.jar: 1 vulnerabilities (highest severity is: 8.8) - autoclosed
Jan 1, 2025
✔️ 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.
Apache Velocity is a general purpose template engine.
Library home page: http://velocity.apache.org/engine/devel/
Path to dependency file: /webapp/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar
Found in HEAD commit: a24c7043a1d471542057baf779a4b949a20ff174
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - velocity-1.7.jar
Apache Velocity is a general purpose template engine.
Library home page: http://velocity.apache.org/engine/devel/
Path to dependency file: /webapp/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar,/home/wss-scanner/.m2/repository/org/apache/velocity/velocity/1.7/velocity-1.7.jar
Dependency Hierarchy:
Found in HEAD commit: a24c7043a1d471542057baf779a4b949a20ff174
Found in base branch: master
Vulnerability Details
An attacker that is able to modify Velocity templates may execute arbitrary Java code or run arbitrary system commands with the same privileges as the account running the Servlet container. This applies to applications that allow untrusted users to upload/modify velocity templates running Apache Velocity Engine versions up to 2.2.
Publish Date: 2021-03-10
URL: CVE-2020-13936
CVSS 3 Score Details (8.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Release Date: 2021-03-10
Fix Resolution: org.apache.velocity:velocity-engine-core:2.3
In order to enable automatic remediation, please create workflow rules
In order to enable automatic remediation for this issue, please create workflow rules
The text was updated successfully, but these errors were encountered: