Memory disclosure via incomplete L2CAP response initialization
Published Jun 28, 2022 · Updated Sep 16, 2024
Use of uninitialized data in Zephyr RTOS 2.4.0 through 2.5.x allows local users to read residual memory through an L2CAP response. In le_ecred_conn_req(), partial connection failures omit destination channel identifiers while response storage remains incompletely initialized. The Bluetooth host must process an Enhanced Credit Based Connection request; the reported consequence is confidentiality loss only.
Summary
What happened
Use of uninitialized data in Zephyr RTOS 2.4.0 through 2.5.x allows local users to read residual memory through an L2CAP response. In le_ecred_conn_req(), partial connection failures omit destination channel identifiers while response storage remains incompletely initialized. The Bluetooth host must process an Enhanced Credit Based Connection request; the reported consequence is confidentiality loss only.
The record
- CVE
- CVE-2021-3435
- Published
- Jun 28, 2022
- Updated
- Sep 16, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-908, T1005
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 28, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v2.4.0 <unspecified
- Affected versionversion=v2.5.0 <unspecified
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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