Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 6b36-1.13.8-0ubuntu1 |
| esm-infra-legacy/trusty | DNE | trusty/esm was DNE [trusty was released [6b36-1.13.8-0ubuntu1~14.04]] |
| precise | released | 6b36-1.13.8-0ubuntu1~12.04 |
| trusty | released | 6b36-1.13.8-0ubuntu1~14.04 |
| trusty/esm | DNE | trusty was released [6b36-1.13.8-0ubuntu1~14.04] |
| upstream | needs-triage | |
| utopic | ignored | end of life |
| vivid | released | 6b36-1.13.8-0ubuntu1~15.04.1 |
| vivid/stable-phone-overlay | DNE | |
| vivid/ubuntu-core | DNE |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 7u79-2.5.6-1 |
| esm-infra-legacy/trusty | DNE | trusty/esm was DNE [trusty was released [7u79-2.5.6-0ubuntu1.14.04.1]] |
| precise | released | 7u79-2.5.6-0ubuntu1.12.04.1 |
| trusty | released | 7u79-2.5.6-0ubuntu1.14.04.1 |
| trusty/esm | DNE | trusty was released [7u79-2.5.6-0ubuntu1.14.04.1] |
| upstream | needs-triage | |
| utopic | ignored | end of life |
| vivid | released | 7u79-2.5.6-0ubuntu1.15.04.1 |
| vivid/stable-phone-overlay | DNE | |
| vivid/ubuntu-core | DNE |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 8u66-b17-1 |
| esm-infra-legacy/trusty | DNE | |
| precise | DNE | |
| trusty | DNE | |
| trusty/esm | DNE | |
| upstream | needs-triage | |
| utopic | ignored | end of life |
| vivid | ignored | end of life |
| vivid/stable-phone-overlay | DNE | |
| vivid/ubuntu-core | DNE |
Показывать по
5 Medium
CVSS2
Связанные уязвимости
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.
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.
The RC4 algorithm, as used in the TLS protocol and SSL protocol, does ...
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.
5 Medium
CVSS2