dbcve.org
Mimosa Management PlatformApplication · Airspan

CVE-2022-0138

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 has a deserialization function that does not validate or check the data, allowing arbitrary classes to be created.

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 confidence

This is an insecure deserialization vulnerability where a deserialization function lacks input validation, allowing an attacker to instantiate arbitrary classes. This could enable remote code execution or other attacks by manipulating serialized data.

MitigationUpgrade to the fixed versions: MMP v1.0.3 or later, PTP C-series v2.8.6.1 or later, and PTMP C-series/A5x v2.5.4.1 or later. If upgrading is not immediately possible, restrict network access to affected devices.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify the Airspan product model
    Log into the device or check the product documentation to determine if it is an Mimosa Management Platform (MMP), C6x, C5x, C5c, or A5x device
    Affected if The device is any of these Airspan models and the version is unknown or appears unpatched
  2. Check the MMP version
    For Mimosa Management Platform, access the admin interface and navigate to System > About or check the login page footer for the version number
    Affected if Version is lower than 1.0.3
  3. Check the C-series firmware version
    For C6x, C5x, or C5c devices, access the web interface and go to Status > Device Info, or use SNMP to query sysDescr, or check the CLI output of 'show version'
    Affected if Firmware version is lower than 2.8.6.1
  4. Check the A5x firmware version
    For A5x devices, access the web interface and go to Status > Device Info, or use SNMP to query sysDescr, or check the CLI output of 'show version'
    Affected if Firmware version is lower than 2.5.4.1
  5. Assess network exposure of management interface
    Verify if the device management port (HTTP/HTTPS on typical web ports) is accessible from untrusted networks by reviewing firewall rules or performing a port scan from an external IP
    Affected if The management interface is exposed to the internet or untrusted LAN segments

The environment is affected if any Airspan MMP, C6x, C5x, C5c, or A5x device is running a version below the thresholds (1.0.3 for MMP, 2.8.6.1 for C-series, 2.5.4.1 for A5x) and its management interface is network-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 the fixed versions: MMP v1.0.3 or later, PTP C-series v2.8.6.1 or later, and PTMP C-series/A5x v2.5.4.1 or later. If upgrading is not immediately possible, restrict network access to affected devices.

Recommended fix High confidence

MMP: v1.0.3 | C6x/C5x/C5c: v2.8.6.1 | A5x: v2.5.4.1

  1. 1. Identify the exact Mimosa device model and current firmware/software version currently installed
  2. 2. For Mimosa Management Platform (MMP): 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 deserialization vulnerability is remediated by confirming the new version is running
  8. 8. Follow standard backup procedures before performing firmware upgrades

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

Fix this in Mimosa Management Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0138 — 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-0138 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