GHSA-2jx8-v4hv-gx3h
HIGHGHSA-2jx8-v4hv-gx3h is a high-severity (CVSS 7.5) XML External Entity (XXE) vulnerability in com.epam.reportportal:service-api. O3 Security confirms whether GHSA-2jx8-v4hv-gx3h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
XXE vulnerability in Launch import
Blast Radius
com.epam.reportportal:service-api☕com.epam.reportportal:service-apiReal-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
| Release Date | Affected Projects | Affected Versions | Access Vector | Security Risk |
|---|---|---|---|---|
| Monday, May 4, 2020 | service-api | Every version, starting from 3.1.0 | Remote | Medium |
Impact
Starting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file that uses external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.
Report Portal versions 4.3.12+ and 5.1.1+ disables external entity resolution for theirs XML parser.
We advise our users install the latest releases we built specifically to address this issue.
Patches
Fixed with https://github.com/reportportal/service-api/pull/1201
Binary Download
https://bintray.com/epam/reportportal/service-api/5.1.1 https://bintray.com/epam/reportportal/service-api/4.3.12
Docker Container Download
- RP v4:
docker pull reportportal/service-api:4.3.12 - RP v5:
docker pull reportportal/service-api:5.1.1
Acknowledgement
The issue was reported to Report Portal Team by an external security researcher. Our Team thanks Julien M. for reporting the issue.
For more information
If you have any questions or comments about this advisory email us: [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.epam.reportportal:service-api | ≥ 3.1.0&&< 4.3.12 | 4.3.12 |
| ☕Maven | com.epam.reportportal:service-api | ≥ 5.0.0&&< 5.1.1 | 5.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.epam.reportportal:service-api. 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.
Fix
Update com.epam.reportportal:service-api to 4.3.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jx8-v4hv-gx3h is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-2jx8-v4hv-gx3h 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-2jx8-v4hv-gx3h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2jx8-v4hv-gx3h in your dependencies?
O3 detects GHSA-2jx8-v4hv-gx3h across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.