Traffic interception via missing TLS hostname verification
Published Mar 12, 2020 · Updated Aug 4, 2024
Improper TLS hostname validation in osquery after 2.9.0 and before 4.2.0 allows man-in-the-middle attackers to intercept traffic. The HTTP client enables peer-certificate checks without installing Boost's RFC 2818 callback, so it accepts a valid certificate issued for another hostname. Exploitation requires a network position and no configured root chain of trust, allowing osquery traffic to be read or altered.
Summary
What happened
Improper TLS hostname validation in osquery after 2.9.0 and before 4.2.0 allows man-in-the-middle attackers to intercept traffic. The HTTP client enables peer-certificate checks without installing Boost's RFC 2818 callback, so it accepts a valid certificate issued for another hostname. Exploitation requires a network position and no configured root chain of trust, allowing osquery traffic to be read or altered.
The record
- CVE
- CVE-2020-1887
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- osquery
- Product
- osquery
- Classifications
- CWE-295, CWE-297, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2020CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.9.0
- Affected versionversion=4.2.0
- Affected versionversion=next of 2.9.0 <unspecified
What conditions does exploitation require?
What is affected?
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