Proxy traffic disclosure via RC4 and fixed IVs
Published Dec 21, 2023 · Updated Aug 2, 2024
Cryptographic weakness in blinksocks 3.3.8 allows remote attackers to disclose proxy traffic through the ssr-auth-chain preset. The preset uses RC4 for symmetric encryption at four code paths and supplies a non-random initialization vector to CBC and CFB operations. Exposure requires proxy traffic protected by the affected preset; published sources demonstrate information disclosure but not code execution or service interruption.
Summary
What happened
Cryptographic weakness in blinksocks 3.3.8 allows remote attackers to disclose proxy traffic through the ssr-auth-chain preset. The preset uses RC4 for symmetric encryption at four code paths and supplies a non-random initialization vector to CBC and CFB operations. Exposure requires proxy traffic protected by the affected preset; published sources demonstrate information disclosure but not code execution or service interruption.
The record
- CVE
- CVE-2023-50481
- Published
- Dec 21, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 21, 2023CVE 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