CVE-2017-14394
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 · uneditedOAuth 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 perform phishing via an unvalidated redirect.
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 confidenceThe OAuth 2.0 authorization server in ForgeRock OpenAM 13.5.0-13.5.1 and AM 5.0.0-5.1.1 fails to properly validate the redirect_uri parameter for certain invalid requests, allowing attackers to craft malicious authorization links that bypass redirect validation and redirect users to attacker-controlled sites after authentication.
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 versionCheck the version of ForgeRock Access Management (AM) or OpenAM installed in your environment. For AM 5.x, this is typically found in the AM welcome page or via the /json/serverinfo/* endpoint. For OpenAM 13.x, check the About page or version.txt in the installation directory.Affected if The installed version falls within 5.0.0-5.1.1 (AM) or 13.5.0-13.5.1 (OpenAM)
-
Verify OAuth 2.0 provider is configuredAccess the AM/OpenAM admin console and navigate to: Realms > [Realm Name] > Services > OAuth2 Provider. Confirm the OAuth 2.0 provider service exists and is enabled.Affected if OAuth 2.0 provider service is configured and enabled in the affected version range
-
Check redirect_uri validation configurationIn the OAuth 2.0 provider configuration, locate the setting for 'Redirect URI Validation' or 'URI Validator'. Examine whether strict redirect_uri validation is enforced for authorization requests.Affected if Redirect URI validation is not strictly enforced, or the validator permits bypasses for malformed redirect_uri values
-
Inspect OAuth authorization endpoint behaviorReview the OAuth 2.0 authorization endpoint configuration at Realms > [Realm Name] > Services > OAuth2 > Authorization. Check if the endpoint properly rejects invalid or manipulated redirect_uri parameters.Affected if The authorization endpoint accepts or allows bypass of redirect_uri validation, enabling potential redirection to arbitrary URLs after user authentication
You are affected if you run ForgeRock AM 5.0.0-5.1.1 or OpenAM 13.5.0-13.5.1 with OAuth 2.0 authorization enabled and have not strictly whitelisted redirect_uri values in the OAuth provider configuration.
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 dataUpgrade to a patched version of ForgeRock Access Management that addresses this redirect_uri validation flaw; for now, strictly whitelist allowed redirect_uri values in the OAuth provider configuration.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14394 — 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-14394 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