CVE-2020-13422
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 · uneditedOpenIAM before 4.2.0.3 does not verify if a user has permissions to perform /webconsole/rest/api/* administrative actions.
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 confidenceOpenIAM versions before 4.2.0.3 lack proper authorization checks on /webconsole/rest/api/* endpoints, allowing any authenticated user to execute administrative actions without permission verification. This is a broken access control vulnerability where the REST API accepts requests without validating whether the user has the required privileges.
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>= 4.1.0, < 4.2.0.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed OpenIAM versionLocate the OpenIAM version information in the application admin console under 'About' or 'System Information', or check the version file in the installation directory if accessible.Affected if The installed version is 4.1.0, 4.1.x, 4.2.0, 4.2.0.1, or 4.2.0.2 (any version >= 4.1.0 but < 4.2.0.3).
-
Confirm webconsole REST API endpoint accessibilityAttempt to access or send a request to an endpoint under /webconsole/rest/api/ using a web browser or HTTP client. This may require authentication but not admin privileges.Affected if The endpoint responds with HTTP 200 and returns data or accepts actions, indicating the API is reachable.
-
Test authorization enforcement on REST APILog in as a non-administrative or low-privilege user and attempt to invoke an administrative action through the /webconsole/rest/api/* endpoint, such as user management or system configuration APIs.Affected if The request succeeds and performs the administrative action without returning an authorization error (HTTP 403 or permission denied message).
If the installed OpenIAM version is between 4.1.0 and 4.2.0.2 inclusive and non-administrative users can successfully execute actions via /webconsole/rest/api/* endpoints, the environment is affected by this vulnerability.
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 data4.2.0.3
Upgrade to OpenIAM 4.2.0.3 or later which implements permission verification for administrative REST API endpoints. If immediate upgrade is not possible, consider restricting network access to the webconsole or implementing a WAF rule to limit API access to authorized IP addresses.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13422 — 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-2020-13422 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