CVE-2022-21176
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 · uneditedMMP: 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, which may allow an attacker to perform a SQL injection and obtain sensitive information.
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 confidenceSQL injection vulnerability in multiple Cambium Networks product lines (MMP, PTP C-series, PTMP C-series and A5x) due to improper user input sanitization. Attackers can exploit this to inject malicious SQL queries and extract sensitive data from the database.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Airspan Mimosa Management Platform (MMP) versionLog into the MMP web interface and navigate to the About or System Information page. Alternatively, access the MMP server via SSH and run: cat /opt/mimosa/mmp/version or check the installed package version.Affected if MMP version is lower than 1.0.3 and the web interface is accessible
-
Identify Airspan C5x or C5c firmware versionLog into the device web interface and check the Status or System page for firmware version. Alternatively, access via CLI (SSH/Telnet) and run: show system info or firmware show.Affected if Firmware version is lower than 2.8.6.1 and the web interface is accessible
-
Identify Airspan C6x firmware versionLog into the C6x device web interface and check the System or About page. Alternatively, access via CLI and run: show version or show system details.Affected if Firmware version is lower than 2.8.6.1 and the web interface is accessible
-
Identify Airspan A5x firmware versionLog into the A5x device web interface and navigate to Status or System Information. Alternatively, access via CLI and run: show system or cat /proc/version if available.Affected if Firmware version is lower than 2.5.4.1 and the web interface is accessible
-
Verify management interface accessibilityDetermine if the web-based management interface (HTTP/HTTPS) for the identified product is exposed to the network. Check firewall rules, NAT configurations, or VLAN settings that may allow external access.Affected if The management interface is reachable from untrusted networks (such as the internet or guest VLANs)
You are affected if any Airspan MMP, C5x, C5c, C6x, or A5x device in your environment is running a version below the specified thresholds AND its web management interface is network-accessible.
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
Apply vendor-provided patches: upgrade MMP to v1.0.3+, PTP C-series to v2.8.6.1+, and PTMP C-series/A5x to v2.5.4.1+. If patching is not immediately possible, audit and restrict network access to these devices to reduce attack surface.
MMP v1.0.3, C6x/C5x/C5c firmware v2.8.6.1, A5x firmware v2.5.4.1
- Identify the specific Mimosa product in use (MMP, C6x, C5x, C5c, or A5x)
- Access the device management interface or MMP admin console
- Verify the current firmware/software version
- Download the appropriate fixed version from Mimosa's official support channels: MMP v1.0.3, C6x/C5x/C5c firmware v2.8.6.1, or A5x firmware v2.5.4.1
- Follow the standard firmware upgrade procedure via the web interface or management console
- After upgrade, verify the new version is installed and the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21176 — 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-21176 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