The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data…
No fixed version listed yet.Check the vendor advisory. References ↓
A remote attacker who can sniff network traffic can conduct plaintext-recovery attacks against the initial bytes of a stream, using a brute-force approach over LSB values, when the traffic happens to rely on keys affected by the Invariance Weakness, and no authentication or user interaction is required.
Official description · CVE.org
The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the "Bar Mitzvah" issue.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 1 Apr 2015. No public exploit code or confirmed exploitation is recorded.
What security researchers reported
Not named in any threat report yetAlso mentioned in 6 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- OperationMalformed19 Oct 2026
- credit: OctoSeek [•Sakula Rat | Porn Name Change•]15 May 2026
- treaty8[.]ca2 Aug 2024
- Alberta NDP2 Jul 2024
- Sakula RAT | Porn name change>>brassiere.world | Orbiters1 Jul 2024
- Sakula RAT | Porn name change>>brassiere.world | Orbiters29 Jun 2024