CVE-2022-21215
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 · uneditedThis vulnerability could allow an attacker to force the server to create and execute a web request granting access to backend APIs that are only accessible to the Mimosa MMP server, or request pages that could perform some actions themselves. The attacker could force the server into accessing routes on those cloud-hosting platforms, accessing secret keys, changing configurations, etc. Affecting 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.
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 confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in Mimosa wireless bridge devices (MMP, PTP C-series, PTMP C-series and A5x). An unauthenticated attacker can force the device to make arbitrary HTTP requests to internal/cloud services, bypassing network segmentation and allowing access to backend APIs, secret keys, and configuration interfaces that should be inaccessible.
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 the device modelAccess the device web interface or CLI and identify whether the device is an Airspan Mimosa product: MMP (Management Platform), C6x, C5x, C5c, or A5x. Check the device label, web login page, or CLI output for the model identifier.Affected if The device model is one of: MMP, C6x, C5x, C5c, or A5x.
-
Determine the firmware or software versionFor MMP (Management Platform): Log into the web interface and navigate to the About or System Information page to find the software version. For C-series (C6x, C5x, C5c) and A5x devices: Access the web interface and look for the firmware version in the Status, Device Info, or System settings section.Affected if The installed version is less than 1.0.3 for MMP, less than 2.8.6.1 for C6x/C5x/C5c, or less than 2.5.4.1 for A5x.
-
Verify web management interface accessibilityConfirm whether the device web management interface (HTTP/HTTPS) is reachable from untrusted networks. Check firewall rules, ACLs, and NAT configurations to determine if the management port is exposed to the internet or an untrusted LAN segment.Affected if The web management interface is accessible from an untrusted network, enabling an unauthenticated attacker to trigger the SSRF.
-
Review HTTP request loggingCheck any available logs on the MMP or device firmware for suspicious outbound HTTP requests originating from the device itself. Look for requests to internal IP ranges (10.x.x.x, 192.168.x.x, 172.16-31.x.x) or cloud service endpoints that were not initiated by legitimate administrators.Affected if Logs show unexpected outbound HTTP requests from the device to internal addresses or cloud services that were not initiated by authorized users.
The device is affected if it is an Airspan Mimosa MMP, C6x, C5x, C5c, or A5x running a version below the fixed releases AND the web management interface is accessible to unauthenticated users.
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
Update affected devices to the patched 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. Apply network segmentation to isolate management interfaces from untrusted networks as an additional safeguard.
MMP: v1.0.3 | C6x/C5x/C5c: v2.8.6.1 | A5x: v2.5.4.1
- 1. Identify the affected Mimosa device or platform in your environment
- 2. For Mimosa Management Platform (MMP): Upgrade to version 1.0.3 or later
- 3. For C6x, C5x, or C5c devices (PTP C-series): Upgrade firmware to version 2.8.6.1 or later
- 4. For A5x devices (PTMP C-series): Upgrade firmware to version 2.5.4.1 or later
- 5. Verify the upgrade was successful by confirming the new version numbers
- 6. After upgrading, restrict network access to the management interfaces to minimize exposure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21215 — 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-21215 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