Protected-data exposure via phased-out TLS cipher suites
Published Jul 2, 2024 · Updated Aug 2, 2024
Risky cryptography in Kiloview P1/P2 firmware 4.8.2605 and earlier allows remote attackers to read protected data via weak TLS ciphers. The embedded server enables at least one TLS cipher suite designated for phaseout, but the published record identifies neither the suite nor the TLS endpoint. Exploitation requires adjacent-network access and high attack complexity; the reported consequence is confidentiality loss without integrity or service impact.
Summary
What happened
Risky cryptography in Kiloview P1/P2 firmware 4.8.2605 and earlier allows remote attackers to read protected data via weak TLS ciphers. The embedded server enables at least one TLS cipher suite designated for phaseout, but the published record identifies neither the suite nor the TLS endpoint. Exploitation requires adjacent-network access and high attack complexity; the reported consequence is confidentiality loss without integrity or service impact.
The record
- CVE
- CVE-2023-41927
- Published
- Jul 2, 2024
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327, CAPEC-97
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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