CVE-2021-37153
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 · uneditedForgeRock Access Management (AM) before 7.0.2, when configured with Active Directory as the Identity Store, has an authentication-bypass issue.
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 confidenceForgeRock Access Management before version 7.0.2 contains an authentication bypass vulnerability when configured to use Active Directory as the identity store. An attacker could potentially bypass authentication mechanisms and gain unauthorized access to protected resources without proper credentials.
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>= 6.0.0, < 7.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ForgeRock Access Management installationLocate the ForgeRock AM installation directory or check system inventory for the AM softwareAffected if ForgeRock AM is not installed on the system
-
Determine the installed versionCheck the version file or startup logs in the ForgeRock AM installation directory. Compare against the affected range 6.0.0 to < 7.0.2Affected if The installed version is 6.0.0, 6.5.x, 7.0.0, or 7.0.1 (any version >= 6.0.0 but < 7.0.2)
-
Verify Active Directory is configured as identity storeExamine the ForgeRock AM identity store configuration files, typically found in the realm or directory configuration settings, to determine if Active Directory is the configured data storeAffected if Active Directory is configured as the identity ordata store for authentication
-
Confirm the authentication module uses the identity storeReview the authentication chain or tree configuration to verify that the authentication process queries the Active Directory identity storeAffected if Authentication flows rely on the Active Directory identity store configuration
The environment is affected if ForgeRock Access Management version is 6.0.0 or higher but below 7.0.2 AND Active Directory is configured as the identity store for authentication.
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 · scoped7.0.2
Upgrade ForgeRock Access Management to version 7.0.2 or later. If immediate upgrade is not possible, review authentication configurations and implement additional monitoring on Active Directory authentication paths.
7.0.2 or later
- 1. Review the ForgeRock Access Management 7.0.2 release notes for upgrade considerations and any breaking changes
- 2. Backup your current AM configuration and data store
- 3. Test the upgrade in a non-production environment before deploying to production
- 4. Upgrade ForgeRock Access Management from your current 6.x version to version 7.0.2 or later
- 5. Verify that Active Directory authentication is working correctly after the upgrade
- 6. Confirm the authentication bypass vulnerability is resolved by testing login flows with Active Directory as the identity store
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37153 — 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-2021-37153 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