MMP: Incorrect Authorization
CVE-2022-21141 is a critical-severity incorrect authorization vulnerability in MMP from Airspan Networks, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version v1.0.3 as the first without the flaw, so updating MMP to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 3.16% chance of exploitation within 30 days, higher than 88% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update MMP to v1.0.3 or a later version.
- Update PTP C-series to v2.8.6.1 or a later version.
- Update PTMP C-series and A5x to v2.5.4.1 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Airspan Networks | MMP | before v1.0.3 | v1.0.3 |
| Airspan Networks | PTP C-series | before v2.8.6.1 | v2.8.6.1 |
| Airspan Networks | PTMP C-series and A5x | before v2.5.4.1 | v2.5.4.1 |
| Airspan | Mimosa Management Platform | before 1.0.3 | 1.0.3 |
| Airspan | C6x Firmware | before 2.8.6.1 | 2.8.6.1 |
| Airspan | C5x Firmware | before 2.8.6.1 | 2.8.6.1 |
| Airspan | C5c Firmware | before 2.8.6.1 | 2.8.6.1 |
| Airspan | A5x Firmware | before 2.5.4.1 | 2.5.4.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 10.0 | Critical | CNA (hq.dhs.gov) |
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 10.0 | High | NVD |
Official description
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 checks on multiple API functions. An attacker may gain access to these functions and achieve remote code execution, create a denial-of-service condition, and obtain sensitive information.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/uscert/ics/advisories/icsa-22-034-02Third Party Advisory, US Government Resource
Other vulnerabilities in MMP
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
Recent Incorrect Authorization vulnerabilities
- 7.5 High severity
- 9.8 Critical severity
- 7.2 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.3 Critical severity
Spotted an error? Tell us.