Proximal privilege escalation via missing WPS bounds check
Published Dec 25, 2021 · Updated Aug 4, 2024
An out-of-bounds write in MediaTek Wi-Fi driver 7.4.0.0 allows physically proximate attackers to gain elevated privileges through WPS. The driver omits a bounds check when processing WPS input and writes beyond the intended memory buffer. Exploitation requires WPS to be used and user interaction, and the resulting memory corruption grants elevated privileges on the device.
Summary
What happened
An out-of-bounds write in MediaTek Wi-Fi driver 7.4.0.0 allows physically proximate attackers to gain elevated privileges through WPS. The driver omits a bounds check when processing WPS input and writes beyond the intended memory buffer. Exploitation requires WPS to be used and user interaction, and the resulting memory corruption grants elevated privileges on the device.
The record
- CVE
- CVE-2021-37560
- Published
- Dec 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 25, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo