CVE-2022-47551
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 · uneditedApiman 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.
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 confidenceApiman Manager REST API versions 1.5.7 through 2.2.3.Final have insufficient authorization checks for read permissions. The vulnerability stems from a large contribution that was not fully compatible with the pre-3.0.0 security model, allowing unauthorized users to potentially read restricted data through the REST API.
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>= 1.5.7, <= 2.2.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Apiman Manager versionCheck the war file name, pom.xml dependency version, or the manifest file in the Apiman manager web application. Common locations: $APIMAN_HOME/manager/war/ or check the manager-api jar/war version.Affected if The installed version falls within >= 1.5.7 and <= 2.2.3.Final
-
Confirm REST API endpoint is accessibleVerify the Apiman Manager REST API endpoint is exposed (typically at /apiman/ or /api/). Check server configuration files (standalone.xml, web.xml) for servlet mappings.Affected if The REST API endpoint is reachable from untrusted networks or non-admin users can access the API URL
-
Verify authorization configuration for read operationsReview the API authorization settings in the Apiman configuration. Check if read permission checks are properly enforced for REST API endpoints returning restricted data.Affected if REST API returns restricted data to users lacking read permission on protected resources
-
Check user role assignmentsReview which users are assigned roles and whether non-privileged users can access the Manager REST API.Affected if Users without admin or proper read permissions can access restricted endpoints
You are affected if your installed Apiman Manager version is between 1.5.7 and 2.2.3.Final and the REST API is accessible to users who should not have read access to restricted data.
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 · scopedUpgrade to Apiman 3.0.0.Final or later, which is not affected by this vulnerability. For organizations unable to upgrade, review and harden REST API permission checks to ensure proper authorization validation before returning any data.
3.0.0.Final
- Upgrade Apiman to version 3.0.0.Final or later to resolve the insufficient permission checks in the Manager REST API
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47551 — 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-2022-47551 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