CVE-2017-14395
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 · uneditedAuth 2.0 Authorization Server of ForgeRock Access Management (OpenAM) 13.5.0-13.5.1 and Access Management (AM) 5.0.0-5.1.1 does not correctly validate redirect_uri for some invalid requests, which allows attackers to execute a script in the user's browser via reflected XSS.
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 · high confidenceThe Auth 2.0 Authorization Server in ForgeRock Access Management (OpenAM) 13.5.0-13.5.1 and AM 5.0.0-5.1.1 contains a reflected XSS vulnerability due to improper validation of the redirect_uri parameter in authorization requests. When processing certain invalid redirect_uri values, the server reflects unvalidated input back to the user's browser, allowing execution of arbitrary script code.
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>= 5.0.0, <= 5.1.1>= 13.5.0, <= 13.5.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 ForgeRock product and versionLocate the installed version of ForgeRock Access Management or OpenAM. Check the AM/OpenAM admin console, or look for version files in the installation directory (typically in the /opt/openam or /opt/AM directory, or check the about page in the admin console at /AM/console/about). Compare the version number to the affected ranges: OpenAM 13.5.0-13.5.1 or AM 5.0.0-5.1.1.Affected if The installed version falls within 13.5.0-13.5.1 for OpenAM or 5.0.0-5.1.1 for AM.
-
Verify OAuth2 authorization endpoint is accessibleConfirm the OAuth2 authorization endpoint is enabled and accessible. The endpoint typically follows the pattern /oauth2/authorize or /oauth2/authorize.json. Check the deployment descriptor or the OAuth2 provider configuration in the admin console under Services > OAuth2 Provider.Affected if OAuth2 authorization endpoint is enabled and accessible without additional authentication.
-
Test for reflected XSS in redirect_uri parameterSend a crafted authorization request with an invalid redirect_uri containing a script payload, for example: /oauth2/authorize?response_type=code&client_id=test&redirect_uri=<script>alert(1)</script>. Inspect the response to see if the redirect_uri value is reflected without proper encoding or validation.Affected if The response reflects the redirect_uri parameter value unencoded or unvalidated in an error message or redirect location.
-
Check redirect_uri validation configurationReview the OAuth2 provider settings in the ForgeRock admin console under OAuth2 Provider > Client Settings. Look for redirect URI validation settings, specifically whether there is an allowlist enforced and whether invalid URIs trigger proper rejection without reflection.Affected if No redirect URI allowlist is configured, or the validation allows arbitrary values to pass through and be reflected in responses.
You are affected if your ForgeRock OpenAM version is 13.5.0-13.5.1 or AM version is 5.0.0-5.1.1 AND the OAuth2 authorization endpoint is accessible and reflects the redirect_uri parameter without proper validation or encoding.
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.
From vendor dataApply the vendor patch to update to a fixed version of ForgeRock AM/OpenAM that properly validates redirect_uri parameters before reflecting them in responses. Validate all redirect URIs against an allowlist and ensure proper encoding of any reflected parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14395 — 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-2017-14395 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