CVE-2022-25842 is a medium-severity (CVSS 6.9) Path Traversal vulnerability in com.alibaba.oneagent:one-java-agent-plugin. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.alibaba.oneagent:one-java-agent-plugin — see the affected versions and patch details below.
Arbitrary File Write via Archive Extraction (Zip Slip)
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
com.alibaba.oneagent:one-java-agent-pluginReal-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
All versions of package com.alibaba.oneagent:one-java-agent-plugin are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) using a specially crafted archive that holds directory traversal filenames (e.g. ../../evil.exe). The attacker can overwrite executable files and either invoke them remotely or wait for the system or user to call them, thus achieving remote command execution on the victim’s machine.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.alibaba.oneagent:one-java-agent-plugin | all versions | 0.0.2com.alibaba.oneagent:one-java-agent-plugin:0.0.2 |
Affected Products
one-java-agentalibabagroupResearch 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 com.alibaba.oneagent:one-java-agent-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.alibaba.oneagent:one-java-agent-plugin to 0.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25842 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2022-25842 in your dependencies?
Find it across Maven, including transitive dependencies.