dbcve.org
Web Policy AgentsApplication · Forgerock

CVE-2023-0339

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-28
Fix available
A fix is available. Upgrade to after 5.10.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Relative Path Traversal vulnerability in ForgeRock Access Management Web Policy Agent allows Authentication Bypass. This issue affects Access Management Web Policy Agent: all versions up to 5.10.1

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 confidence

A relative path traversal vulnerability in ForgeRock Access Management Web Policy Agent allows attackers to bypass authentication by manipulating file paths using '..' sequences to access restricted resources outside the intended web root.

MitigationUpgrade ForgeRock Access Management Web Policy Agent to version 5.10.2 or later to obtain the patch for this vulnerability.

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
Web Policy AgentsApplication
Affected:<= 5.10.1

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Web Policy Agent installation location
    Locate the ForgeRock Web Policy Agent installation directory. Common paths include /opt/forgerock/web-agent or within the web container's webapps directory. Look for files named agent.conf, bootstrap.properties, or AMAgent.properties.
    Affected if The Web Policy Agent is installed on the system.
  2. Check agent version from configuration files
    Open the agent configuration file (agent.conf or AMAgent.conf) and look for a version parameter. Alternatively, check the agent's bootstrap.properties file which typically contains a version or build number entry.
    Affected if The version listed is 5.10.1 or lower.
  3. Verify agent JAR file version
    Locate the agent's core JAR files in the installation directory (typically in a lib or agent/lib folder). Use the command 'java -jar agent-core.jar --version' if available, or inspect the MANIFEST.MF file within the JAR for the Implementation-Version attribute.
    Affected if The JAR version manifests as 5.10.1 or any version below 5.10.2.
  4. Check agent log for version startup message
    Review the Web Policy Agent debug or audit logs. Search for log entries at agent startup that contain version information, typically displaying 'Web Policy Agent version: X.X.X' or similar.
    Affected if The logged version is 5.10.1 or earlier.

You are affected if a ForgeRock Web Policy Agent is installed and its version is 5.10.1 or lower, as versions prior to 5.10.2 contain the path traversal vulnerability in the web policy agent component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.10.1
Interim mitigation

Upgrade ForgeRock Access Management Web Policy Agent to version 5.10.2 or later to obtain the patch for this vulnerability.

Recommended fix High confidence

Web Policy Agent 5.10.2 or later

  1. 1. Identify the current Web Policy Agent version in your deployment
  2. 2. Download the fixed Web Policy Agent version (5.10.2 or later) from backoffice.forgerock.com or the official ForgeRock download portal
  3. 3. Review the ForgeRock release notes for version 5.10.2 for any specific migration or configuration requirements
  4. 4. Back up your current Web Policy Agent configuration directory
  5. 5. Stop the web server or service running the Web Policy Agent
  6. 6. Install the new Web Policy Agent version following the standard installation procedure
  7. 7. Restore or adapt your configuration as needed based on release notes
  8. 8. Start the web server or service
Caveat Review release notes for any configuration changes between 5.10.1 and 5.10.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Web Policy Agents Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-0339 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-0339 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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