CVE-2022-38723 — gravitee-api-management
HIGHCVE-2022-38723 is a high-severity (CVSS 8.6) Path Traversal vulnerability in io.gravitee.apim:gravitee-api-management. A fix is available for io.gravitee.apim:gravitee-api-management — see the affected versions and patch details below.
Gravitee API Management contains Path Traversal
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-38723.
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
io.gravitee.apim:gravitee-api-managementReal-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
This CVE addresses the partial fix for CVE-2019-25075
Gravitee API Management before 3.15.13 allows path traversal through HTML injection. A certain HTML injection combined with path traversal in the Email service in Gravitee API Management before 3.15.13 allows anonymous users to read arbitrary files via a /management/users/register request.
A patch was published in 2019 for this vulnerability but did not appear to have solved the issue. Version 3.15.13 did remove the flaw.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.gravitee.apim:gravitee-api-management | all versions | 3.15.13io.gravitee.apim:gravitee-api-management:3.15.13 |
Affected Products
api managementgraviteeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.gravitee.apim:gravitee-api-management, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.gravitee.apim:gravitee-api-management to 3.15.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-38723 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2022-38723 in your dependencies?
Find it across Maven, including transitive dependencies.