CVE-2015-2808
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 73.9% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 73.9% in the next 30 days (EPSS).
- Severity: 3.7 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 73.9% · EPSS, next 30 days
- Weakness
- CWE-327 · Broken cryptographic algorithm
- Record status
- Modified
Affected
- Oracle Communications Application Session Controller ≤ 3.9.0
- Oracle Communications Policy Management < 9.9.2
- Oracle Http Server 11.1.1.7.0
- Oracle Http Server 11.1.1.9.0
- Oracle Http Server 12.1.3.0.0
- Oracle Http Server 12.2.1.1.0
- Oracle Http Server 12.2.1.2.0
- Oracle Integrated Lights Out Manager Firmware ≤ 3.2.11
Attack profile CVSS 3.1 · 3.7
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2015-2808.md and follow it. Check whether this project is affected by CVE-2015-2808. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
- http://www.oracle.com/technetwork/security-advisory/cpujan2018-3236628.html
References
- http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04779034
- http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10705
- http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10727
- http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00013.html
- http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00014.html
- http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00015.html
- http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00022.html
- http://lists.opensuse.org/opensuse-security-announce/2015-06/msg00031.html
- http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00039.html
- http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00040.html
- http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00046.html
- http://lists.opensuse.org/opensuse-security-announce/2015-07/msg00047.html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00000.html
- http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00004.html
- http://lists.opensuse.org/opensuse-security-announce/2016-01/msg00005.html
- http://marc.info/?l=bugtraq&m=143456209711959&w=2
- http://marc.info/?l=bugtraq&m=143629696317098&w=2
- http://marc.info/?l=bugtraq&m=143741441012338&w=2
- http://marc.info/?l=bugtraq&m=143817021313142&w=2
- http://marc.info/?l=bugtraq&m=143817899717054&w=2
- http://marc.info/?l=bugtraq&m=143818140118771&w=2
- http://marc.info/?l=bugtraq&m=144043644216842&w=2
- http://marc.info/?l=bugtraq&m=144059660127919&w=2
- http://marc.info/?l=bugtraq&m=144059703728085&w=2
- http://marc.info/?l=bugtraq&m=144060576831314&w=2