Service interruption via incorrect IEEE 1905 bounds check
Published Dec 25, 2021 · Updated Aug 4, 2024
An out-of-bounds read in MediaTek 1905 daemon 2.0.2 allows physically proximate attackers to cause a service interruption via IEEE 1905 traffic. The daemon applies an incorrect bounds check while parsing IEEE 1905 input, permitting a read beyond the intended buffer. Exploitation requires Wi-Fi EasyMesh R2, but no privileges or user interaction, and results in denial of service.
Summary
What happened
An out-of-bounds read in MediaTek 1905 daemon 2.0.2 allows physically proximate attackers to cause a service interruption via IEEE 1905 traffic. The daemon applies an incorrect bounds check while parsing IEEE 1905 input, permitting a read beyond the intended buffer. Exploitation requires Wi-Fi EasyMesh R2, but no privileges or user interaction, and results in denial of service.
The record
- CVE
- CVE-2021-37567
- Published
- Dec 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499
- 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