SQL injection via buffered pre-TLS client data
Published Aug 25, 2022 · Updated Aug 4, 2024
SQL injection in Yandex Odyssey 1.1 allows man-in-the-middle attackers to execute arbitrary SQL during initial TLS negotiation. The tls.c handshake path failed to reject plaintext remaining in the connection readahead buffer before enabling TLS, so Odyssey forwarded those bytes to PostgreSQL. Exposure requires certificate Common Name client authentication and a network position between the client and Odyssey; injected queries execute with the routed database session's authority.
Summary
What happened
SQL injection in Yandex Odyssey 1.1 allows man-in-the-middle attackers to execute arbitrary SQL during initial TLS negotiation. The tls.c handshake path failed to reject plaintext remaining in the connection readahead buffer before enabling TLS, so Odyssey forwarded those bytes to PostgreSQL. Exposure requires certificate Common Name client authentication and a network position between the client and Odyssey; injected queries execute with the routed database session's authority.
The record
- CVE
- CVE-2021-43766
- Published
- Aug 25, 2022
- Updated
- Aug 4, 2024
- Vendor
- Yandex
- Product
- Odyssey
- Classifications
- CWE-89, CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2022CVE 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=Odyssey 1.1
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