CVE-2022-38723
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGravitee API Management before 3.15.13 allows path traversal through HTML injection.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGravitee API Management before version 3.15.13 contains a path traversal vulnerability that is exploitable through HTML injection. An attacker could potentially manipulate file paths to access sensitive files outside the intended web root directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.15.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Gravitee API Management versionCheck the version by inspecting the graviteeam-gateway or graviteeam-api service/jar file, or query the /management/tenants API endpoint if the management API is accessible. Common locations include /opt/graviteeio/apim/gateway or the Docker container labels.Affected if Installed version is earlier than 3.15.13 (for example, 3.15.0, 3.14.0, 3.13.x, etc.)
-
Verify management API is externally accessibleCheck the API Gateway configuration (typically in gravitee.yml or environment variables) to determine if the Management API or Console is exposed to untrusted networks rather than being restricted to localhost/internal network.Affected if The Management REST API or Console is reachable from outside the trusted network, enabling the HTML injection attack vector
-
Confirm path traversal attack surface existsReview API endpoint configurations that handle file paths or accept user-supplied path parameters, particularly those related to API documentation, custom extensions, or file storage features.Affected if Custom scripts, extensions, or file handling endpoints that accept path parameters are enabled and accessible without additional authentication controls
You are affected if Gravitee API Management version is below 3.15.13 AND the Management API is externally accessible, allowing an attacker to exploit the path traversal through HTML injection to access files outside the web root.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.15.3
Upgrade Gravitee API Management to version 3.15.13 or later to remediate this vulnerability. Verify the upgrade in a staging environment before production deployment.
Gravitee API Management 3.15.13 or later
- Backup your Gravitee API Management instance and database
- Review Gravitee upgrade documentation for version 3.15.x migration requirements
- Download Gravitee API Management version 3.15.13 or later from the official Gravitee repository
- Stop the Gravitee API Management services
- Execute the upgrade following the documented upgrade procedure for your deployment method (ZIP, Docker, or Kubernetes)
- Restart the Gravitee API Management services
- Verify the installation by checking the version number and testing API functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38723 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38723 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data