dbcve.org
Mimosa Management PlatformApplication · Airspan

CVE-2022-21143

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 1.0.3 / 2.5.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
MMP: 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 properly sanitize user input on several locations, which may allow an attacker to inject arbitrary commands.

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 confidence

Command injection vulnerability in Ubiquiti wireless products (MMP, PTP C-series, PTMP C-series and A5x) where improper sanitization of user input across multiple locations allows attackers to inject arbitrary commands.

MitigationUpgrade to vendor-supplied patched versions: MMP v1.0.3 or later, PTP C-series v2.8.6.1 or later, PTMP C-series and A5x v2.5.4.1 or later.

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
Mimosa Management PlatformApplication
Affected:< 1.0.3
C6x FirmwareOperating system
Affected:< 2.8.6.1
C5x FirmwareOperating system
Affected:< 2.8.6.1
C5c FirmwareOperating system
Affected:< 2.8.6.1
A5x FirmwareOperating system
Affected:< 2.5.4.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Airspan product variant
    Access the device web interface, CLI via SSH, or check network inventory to determine the exact model (MMP, C6x, C5x, C5c, or A5x)
    Affected if The device is any of these models and the variant cannot be determined for version checking
  2. Check the firmware version for MMP
    For Mimosa Management Platform: log into the web interface and navigate to Settings > About, or query the management API for the version endpoint. Compare the version number to 1.0.3
    Affected if Version is lower than 1.0.3
  3. Check the firmware version for C-series devices
    For C6x, C5x, or C5c: access the device web UI, go to Device > Status, or use CLI command 'show version'. Compare firmware version to 2.8.6.1
    Affected if Version is lower than 2.8.6.1
  4. Check the firmware version for A5x devices
    For A5x: access the device web UI via the management IP, check Device > Status page, or use CLI 'show version'. Compare firmware version to 2.5.4.1
    Affected if Version is lower than 2.5.4.1
  5. Verify management interface exposure
    Check if the device management web interface (typically ports 80/443 or custom ports) is accessible from untrusted networks or the public internet using nmap or a browser
    Affected if The management interface is exposed to untrusted networks and the version is in the affected range

The environment is affected if any Airspan Mimosa MMP, C6x, C5x, C5c, or A5x device is running firmware below the patched versions (1.0.3, 2.8.6.1, or 2.5.4.1 respectively) and has its management interface accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.3 / 2.5.4.1 / 2.8.6.1 or later
Fixed in 1.0.32.5.4.12.8.6.1
Interim mitigation

Upgrade to vendor-supplied patched versions: MMP v1.0.3 or later, PTP C-series v2.8.6.1 or later, PTMP C-series and A5x v2.5.4.1 or later.

Recommended fix Moderate confidence

MMP v1.0.3; C6x/C5x/C5c firmware v2.8.6.1; A5x firmware v2.5.4.1

  1. 1. Identify the Mimosa device model and current firmware version via the web interface or CLI
  2. 2. For MMP (Management Platform): Upgrade to version 1.0.3 or later
  3. 3. For C6x devices: Upgrade firmware to version 2.8.6.1 or later
  4. 4. For C5x devices: Upgrade firmware to version 2.8.6.1 or later
  5. 5. For C5c devices: Upgrade firmware to version 2.8.6.1 or later
  6. 6. For A5x devices: Upgrade firmware to version 2.5.4.1 or later
  7. 7. After upgrade, verify the new version is running and test that the command injection vulnerability is no longer exploitable
Caveat Review release notes for any changes to configuration or functionality before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mimosa Management Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21143 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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