OpenDJ unauthenticated SSRF, local file read and unbounded-read DoS in the DSMLv2 gateway
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.openidentityplatform.opendj:opendj-dsml-servlet 5.1.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.openidentityplatform.opendj:opendj-dsml-servlet
- Affected
- <= 5.1.1
- Fixed in
- 5.1.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-68r5-9hpg-7qw9 lists affected ranges: Maven org.openidentityplatform.opendj:opendj-dsml-servlet >=0 <=5.1.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.4 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
The DSMLv2 SOAP gateway (opendj-dsml-servlet) in OpenIdentityPlatform OpenDJ through 5.1.1 dereferences attacker-supplied xsd:anyURI values server-side without a scheme allowlist, egress filtering, or a size cap, and is reachable without authentication by default. A remote unauthenticated attacker can submit a DSML add/modify request whose value is a URI to (1) perform server-side request forgery against internal services and the cloud metadata endpoint (SSRF), (2) read local files via file: URIs, and (3) exhaust memory through an unbounded response read (DoS). Fixed in 5.1.2: anyURI dereferencing is disabled by default; when enabled it is limited to an http/https allowlist, rejects loopback/link-local/private/reserved targets, refuses HTTP redirects, and caps the bytes read. The gateway also now requires container-managed authentication by default.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-68r5-9hpg-7qw9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-68r5-9hpg-7qw9 Advisory: OpenDJ unauthenticated SSRF, local file read and unbounded-read DoS in the DSMLv2 gateway IDs: GHSA-68r5-9hpg-7qw9 Record: https://patchnext.com/advisories/ghsa-68r5-9hpg-7qw9 (revision 1, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.4) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.openidentityplatform.opendj:opendj-dsml-servlet 5.1.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.openidentityplatform.opendj:opendj-dsml-servlet: affected <= 5.1.1; fixed in 5.1.2 ## Suggested inspection (read-only) - Maven org.openidentityplatform.opendj:opendj-dsml-servlet: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.openidentityplatform.opendj:opendj-dsml-servlet. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-68r5-9hpg-7qw9 (GitHub-reviewed advisory GHSA-68r5-9hpg-7qw9 lists affected ranges: Maven org.openidentityplatform.opendj:opendj-dsml-servlet >=0 <=5.1.1) Commands are suggestions: review each one before running it.
Loading voting…