CVE-2022-47551: Apiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST A

Routine

MEDIUM 6.5UPGRADE

CVE-2022-47551 is a medium-severity flaw (CVSS 6.5) affecting apiman. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Apiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. The root cause of the issue is the Apiman project's accidental acceptance of a large contribution that was not fully compatible with the security model of Apiman versions before 3.0.0.Final. Because of this, 3.0.0.Final is not affected by the vulnerability.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-276
Published	2022-12-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: apiman

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

Am I affected?

Timeline

2022-12-20 00:15 UTCPublished CVE record published
2026-06-17 05:13 UTCUpdated Record last modified

apiman apiman UPGRADE

Affected: >= 1.5.7 and <= 2.2.3

Fixed in: newer than 2.2.3

Safe to downgrade to: a release before 1.5.7

1. Check installed version

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

2. UPGRADE to newer than 2.2.3 (Debian / Ubuntu)

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade apiman

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 1.5.7 (Debian / Ubuntu)

apt-cache madison apiman sudo apt install apiman=<VERSION_BEFORE_1.5.7> sudo apt-mark hold apiman

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

dnf --showduplicates list apiman sudo dnf downgrade apiman-<VERSION_BEFORE_1.5.7> sudo dnf versionlock add apiman

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-2022-47551?

apiman: upgrade to newer than 2.2.3. Exact commands for each OS are on this page.

Is CVE-2022-47551 being exploited?

CVE-2022-47551 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-2022-47551 affect?

CVE-2022-47551 affects apiman. Severity is medium (CVSS 6.5). Apiman 1.5.7 through 2.2.3.Final has insufficient checks for read permissions within the Apiman Manager REST API. The root cause of the issue is the Apiman project's accidental acceptance of a large contribution that was not fully compatibl

How urgent is CVE-2022-47551?

Priority 35/100. No elevated risk signals yet.

Related CVEs

CVE-2023-28640 MEDIUM 6.4 DOWNGRADE Apiman is a flexible and open source API Management platform

References

← Back to latest CVEs