CVE-2023-50572 is a medium-severity (CVSS 5.5) Out-of-bounds Write vulnerability in org.jline:jline-parent. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.jline:jline-parent — see the affected versions and patch details below.
JLine vulnerable to out of memory error
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-50572.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jline:jline-parentReal-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 issue in the component GroovyEngine.execute of JLine v3.24.1 allows attackers to cause an out of memory (OOM) error exception.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jline:jline-parent | all versions | 3.25.0org.jline:jline-parent:3.25.0 |
Affected Products
jlinejlineResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jline:jline-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jline:jline-parent to 3.25.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-50572 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is CVE-2023-50572 in your dependencies?
Find it across Maven, including transitive dependencies.