CVE-2022-21196
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 and authentication checks on multiple API routes. An attacker may gain access to these API routes 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 · high confidenceMultiple API routes in Ubiquiti MIMO Mesh (MMP), PTP C-series, and PTMP C-series/A5x devices lack proper authentication and authorization checks. This allows unauthenticated attackers to access sensitive API endpoints, potentially achieving remote code execution, causing denial-of-service, or exfiltrating sensitive data.
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 device model and firmware versionAccess the device web interface or CLI and retrieve the system information or firmware version (typically found in Settings > System, or via 'show version' or 'status' command)Affected if The device is an Airspan Mimosa Management Platform, C6x, C5x, C5c, or A5x, and the firmware version is lower than 1.0.3 (MMP), 2.8.6.1 (C-series), or 2.5.4.1 (A5x)
-
Verify API endpoint accessibilityAttempt to access common API paths (such as /api, /cgi-bin/api, or vendor-specific endpoints) from an unauthenticated browser or via curl without providing credentialsAffected if HTTP requests to API endpoints return successful responses (200 OK) rather than redirecting to login or returning 401/403 errors
-
Check for unauthenticated API response contentSend a request to suspected API endpoints without authentication headers and examine the response body for sensitive data (configuration details, device status, or administrative functions)Affected if The API returns JSON or XML data containing system configuration, credentials, or administrative options without requiring authentication
-
Confirm device is network accessibleVerify that the device management interface or API ports (typically 80/443) are reachable from untrusted network segments rather than only from a trusted management VLANAffected if The device API is exposed directly to the internet or to untrusted network segments without firewall filtering
A user is affected if their Airspan device is one of the listed models, runs a firmware version below the patched releases, AND the API endpoints are accessible without authentication credentials.
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
Apply vendor-provided firmware updates: MMP to v1.0.3 or later, PTP C-series to v2.8.6.1 or later, PTMP C-series/A5x to v2.5.4.1 or later. If patching is immediately infeasible, restrict API route access via network segmentation and firewall rules.
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 management platform or specific device firmware model)
- Access the device management interface or MMP admin console
- For MMP: Upgrade to version 1.0.3 or later
- For C6x, C5x, or C5c devices: Upgrade firmware to version 2.8.6.1 or later
- For A5x devices: Upgrade firmware to version 2.5.4.1 or later
- After upgrade, verify the authorization fixes are applied by testing API access controls
- Confirm that unauthenticated API routes are no longer accessible without proper credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21196 — 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-21196 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