Skip to content
Fencer Vulns
critical 10.0

CVE-2022-21196 json

Airspan Networks Mimosa Improper Authorization

published 2022-02-18 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-26430

cvss
10.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

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 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.

Patch / fix

  • Airspan Networks MMP v1.0.3
  • Airspan Networks PTP C-series v2.8.6.1
  • Airspan Networks PTMP C-series and A5x v2.5.4.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-034-02 updated cvss 10.0

Airspan Networks Mimosa

  • Airspan Networks MMP < 1.0.3 Airspan Networks PTMP C-series and A5x < 2.5.4.1 Airspan Networks PTP C-series < 2.8.6.1
    affected: mitigation “Update MMP: Version 1.0.4 or later” cloud.mimosa.co

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
18 mo ago

Exploit prediction

3.66% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • Airspan Networks MMP
  • Airspan Networks PTP C-series
  • Airspan Networks PTMP C-series and A5x

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.