Traffic interception via improper server certificate validation
Published Oct 2, 2024 · Updated Oct 2, 2024
Improper certificate validation in Google Android and Nest firmware allows remote attackers to intercept TLS traffic during network connections. The TLS connection initializer fails to authenticate the server certificate, accepting an attacker-controlled endpoint that can read traffic or return modified responses. The attacker must occupy the network path; Nest firmware before 1.73c is affected, while Android's affected version is unspecified.
Summary
What happened
Improper certificate validation in Google Android and Nest firmware allows remote attackers to intercept TLS traffic during network connections. The TLS connection initializer fails to authenticate the server certificate, accepting an attacker-controlled endpoint that can read traffic or return modified responses. The attacker must occupy the network path; Nest firmware before 1.73c is affected, while Android's affected version is unspecified.
The record
- CVE
- CVE-2024-44097
- Published
- Oct 2, 2024
- Updated
- Oct 2, 2024
- Vendor
- Product
- Nest Doorbell (battery) Firmware
- Classifications
- CWE-269, T1638, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 2, 2024CVE publishedPublication date reported by the CVE source.
- Oct 2, 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=0 <1.73c
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.
Weakness, pattern, technique
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