Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-59j4-wjwp-mw9m

HIGH

GHSA-59j4-wjwp-mw9m is a high-severity (CVSS 8.8) vulnerability in org.apache.velocity:velocity-engine-parent. O3 Security confirms whether GHSA-59j4-wjwp-mw9m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sandbox Bypass in Apache Velocity Engine

Also known asCVE-2020-13936
Published
Jan 6, 2022
Updated
Mar 15, 2024
Affected
2 pkgs
Patched
1 / 2
Exploits
None indexed
Exploitation data as of Mar 15, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
org.apache.velocity:velocity-engine-parentorg.apache.velocity:velocity

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.velocity:velocity-engine-parentall versions2.3
Mavenorg.apache.velocity:velocityall versionsNo fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.velocity:velocity-engine-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.velocity:velocity-engine-parent to 2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59j4-wjwp-mw9m is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-59j4-wjwp-mw9m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-59j4-wjwp-mw9m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-59j4-wjwp-mw9m in your dependencies?

O3 detects GHSA-59j4-wjwp-mw9m across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-59j4-wjwp-mw9m: Sandbox Bypass in… | O3 Security