Intel(R) PROSet/Wireless WiFi products: Improper Restriction of Operations within the Bounds of a Memory Buffer
CVE-2022-21160 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in Intel(R) PROSet/Wireless WiFi products, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Intel(R) PROSet/Wireless WiFi products versions: See references. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.87% chance of exploitation within 30 days, higher than 59% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Wireless-ac 9560 Firmware to 22.120 or a later version.
- Update Wireless-ac 9462 Firmware to 22.120 or a later version.
- Update Wireless-ac 9461 Firmware to 22.120 or a later version.
- Read the advisory on intel.com for workarounds and exact fixed builds.
- 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 |
|---|---|---|---|
| Intel(R) PROSet/Wireless WiFi products | Intel(R) PROSet/Wireless WiFi products | See references | Not stated |
| Intel | Wireless-ac 9560 Firmware | before 22.120 | 22.120 |
| Intel | Wireless-ac 9462 Firmware | before 22.120 | 22.120 |
| Intel | Wireless-ac 9461 Firmware | before 22.120 | 22.120 |
| Intel | Wireless-ac 9260 Firmware | before 22.120 | 22.120 |
| Intel | Proset Wi-fi 6e Ax210 Firmware | before 22.120 | 22.120 |
| Intel | Wi-fi 6e Ax211 Firmware | before 22.120 | 22.120 |
| Intel | Wi-fi 6 Ax200 Firmware | before 22.120 | 22.120 |
| Intel | Wi-fi 6 Ax201 Firmware | before 22.120 | 22.120 |
| Intel | Wi-fi 6e Ax411 Firmware | before 22.120 | 22.120 |
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
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 3.1 | 7.5 | High | CISA (ADP) |
Official description
Improper buffer restrictions for some Intel(R) PROSet/Wireless WiFi products may allow an unauthenticated user to potentially enable denial of service via network access.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Intel(R) PROSet/Wireless WiFi products
- 7.5 High severity
- 8.8 High severity
Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.