CVE-2015-7756 json
The encryption implementation in Juniper ScreenOS 6.2.0r15 through 6.2.0r18, 6.3.0r12 before 6.3.0r12b, 6.3.0r13 before 6.3.0r13b, 6.3.0r14…
published 2015-12-19 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7656
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
The encryption implementation in Juniper ScreenOS 6.2.0r15 through 6.2.0r18, 6.3.0r12 before 6.3.0r12b, 6.3.0r13 before 6.3.0r13b, 6.3.0r14 before 6.3.0r14b, 6.3.0r15 before 6.3.0r15b, 6.3.0r16 before 6.3.0r16b, 6.3.0r17 before 6.3.0r17b, 6.3.0r18 before 6.3.0r18b, 6.3.0r19 before 6.3.0r19b, and 6.3.0r20 before 6.3.0r21 makes it easier for remote attackers to discover the plaintext content of VPN sessions by sniffing the network for ciphertext data and conducting an unspecified decryption attack.
Exploit prediction
2.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
kb.juniper.net
/InfoCenter/index?page=content&id=JSA10713
vendor-advisory
- arstechnica.com /security/2015/12/unauthorized-code-in-juniper-firewalls-decrypts-encrypted-vpn-traffic/
- wired.com /2015/12/juniper-networks-hidden-backdoors-show-the-risk-of-government-backdoors/
-
securitytracker.com
/id/1034489
vdb-entry
-
kb.cert.org
/vuls/id/640184
third-party-advisory
- forums.juniper.net /t5/Security-Incident-Response/Important-Announcement-about-ScreenOS/ba-p/285554
- github.com /hdm/juniper-cve-2015-7755
- adamcaudill.com /2015/12/17/much-ado-about-juniper/
- forbes.com /sites/thomasbrewster/2015/12/18/juniper-says-it-didnt-work-with-government-to-add-unauthorized-code-to-networ
Sources
- CVE List CVE-2015-7756
- NVD CVE-2015-7756
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.