Skip to content
Fencer Vulns
medium 6.5

CVE-2022-21800 json

Airspan Networks Mimosa Use of a Broken or Risky Cryptographic Algorithm

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

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
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 uses the MD5 algorithm to hash the passwords before storing them but does not salt the hash. As a result, attackers may be able to crack the hashed passwords.

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 6.5

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
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

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

CVSS scores

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

Affected products

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

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm
  • CWE-326 Inadequate Encryption Strength

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.