CVE-2020-13422: OpenIAM before 4.2.0.3 does not verify if a user has permissions to perform /webconsole/rest/api/* administrat

This month

HIGH 8.1UPGRADE

CVE-2020-13422 is a high-severity flaw (CVSS 8.1) affecting openiam. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

OpenIAM before 4.2.0.3 does not verify if a user has permissions to perform /webconsole/rest/api/* administrative actions.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-862
Published	2021-04-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: openiam

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-04-06 21:15 UTCPublished CVE record published
2026-06-17 02:53 UTCUpdated Record last modified

openiam openiam UPGRADE

Affected: >= 4.1.0 and < 4.2.0.3

Fixed in: 4.2.0.3

Safe to downgrade to: a release before 4.1.0

1. Check installed version

apt-cache policy openiam || rpm -q openiam || openiam --version

2. UPGRADE to 4.2.0.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade openiam

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade openiam

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 4.1.0 (Debian / Ubuntu)

apt-cache madison openiam sudo apt install openiam=<VERSION_BEFORE_4.1.0> sudo apt-mark hold openiam

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list openiam sudo dnf downgrade openiam-<VERSION_BEFORE_4.1.0> sudo dnf versionlock add openiam

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-13422?

openiam: upgrade to 4.2.0.3. Exact commands for each OS are on this page.

Is CVE-2020-13422 being exploited?

CVE-2020-13422 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-13422 affect?

CVE-2020-13422 affects openiam. Severity is high (CVSS 8.1). OpenIAM before 4.2.0.3 does not verify if a user has permissions to perform /webconsole/rest/api/* administrative actions.

How urgent is CVE-2020-13422?

Priority 43/100. High severity

Related CVEs

CVE-2020-13421 CRITICAL 9.8 UPGRADE OpenIAM before 4.2.0.3 has Incorrect Access Control for the Create User, Modify User Permissions, and Password
CVE-2020-13420 CRITICAL 9.8 UPGRADE OpenIAM before 4.2.0.3 allows remote attackers to execute arbitrary code via Groovy Script.
CVE-2020-13419 MEDIUM 5.3 UPGRADE OpenIAM before 4.2.0.3 allows Directory Traversal in the Batch task.
CVE-2020-13418 MEDIUM 6.1 UPGRADE OpenIAM before 4.2.0.3 allows XSS in the Add New User feature.

References

← Back to latest CVEs