CVE-2022-21141
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 · uneditedMMP: All versions prior to v1.0.3, PTP C-series: Device versions prior to v2.8.6.1, and PTMP C-series and A5x: Device versions prior to v2.5.4.1 does not perform proper authorization checks on multiple API functions. An attacker may gain access to these functions and achieve remote code execution, create a denial-of-service condition, and obtain sensitive information.
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 confidenceMultiple Ubiquiti wireless networking products (MMP, PTP C-series, PTMP C-series/A5x) fail to perform authorization checks on various API functions, allowing unauthenticated attackers to access privileged API endpoints and achieve remote code execution, cause denial-of-service, or extract sensitive information.
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.0.3< 2.8.6.1< 2.8.6.1< 2.8.6.1< 2.5.4.1CVSS 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 the Airspan product modelLocate the device label, management console, or SNMP inventory to confirm the exact model (MMP, C6x, C5x, C5c, or A5x).Affected if The product is not one of the listed affected models.
-
Check the firmware versionAccess the device management interface or use the vendor-provided CLI/UI to retrieve the current firmware version. Compare it to the affected ranges: MMP < 1.0.3, C6x/C5x/C5c < 2.8.6.1, A5x < 2.5.4.1.Affected if The installed firmware version is lower than the corresponding fixed version for your product.
-
Assess API interface exposureReview network configuration to determine if the device management API (typically ports 80/443 or vendor-specified management ports) is accessible from untrusted networks or the internet.Affected if The management API is exposed to untrusted networks without firewall restrictions.
-
Verify API authorization controlsIf the API is accessible, attempt to invoke a privileged API endpoint (such as system configuration, status, or administrative functions) without providing authentication credentials.Affected if The API returns sensitive data or allows privileged operations without requiring valid authentication.
You are affected if you are running an Airspan MMP, C6x, C5x, C5c, or A5x device with firmware below the fixed versions and the management API is network-accessible without proper authorization controls.
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 · scoped1.0.32.5.4.12.8.6.1
Upgrade firmware to v1.0.3 (MMP), v2.8.6.1 (PTP C-series), or v2.5.4.1 (PTMP C-series/A5x) to implement proper API authorization controls; restrict network access to management interfaces as interim measure.
MMP v1.0.3, C6x/C5x/C5c firmware v2.8.6.1, A5x firmware v2.5.4.1
- Identify the specific Mimosa product in use (MMP, C6x, C5x, C5c, or A5x)
- Determine the current installed version through the device management interface or system settings
- For Mimosa Management Platform: Upgrade to version 1.0.3 or later
- For C6x, C5x, or C5c firmware: Upgrade to version 2.8.6.1 or later
- For A5x firmware: Upgrade to version 2.5.4.1 or later
- Obtain the appropriate firmware/software from Mimosa's official support channels or trusted distribution point
- Follow Mimosa's standard firmware upgrade procedure for your device model
- After upgrade, verify the new version is installed correctly
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-21141 — 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-21141 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