CVE-2015-5369 juniper pulse connect secure: Code
juniper pulse connect secure: no CVSS score yet. EPSS 1.8% estimated probability of exploitation activity in the next 30 days.
Pulse Connect Secure (aka PCS and formerly Juniper PCS) PSC6000, PCS6500, and MAG PSC360 8.1 before 8.1r5, 8.0 before 8.0r13, 7.4 before 7.4r13.5, and 7.1 before 7.1r22.2 and PPS 5.1 before 5.1R5 and 5.0 before 5.0R13, when Hardware Acceleration is enabled, does not properly validate the Finished TLS handshake message, which makes it easier for remote attackers to conduct man-in-the-middle attacks via a crafted Finished message.
- EPSS
- 1.8% (unchanged from 1.8% a week ago; 1.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 78th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- OWASP Top 10
- A05:2025 Injection
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2015-5369 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-5369?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-5369?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2015-5369 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| juniper:pulse_connect_secure | 5.1 |
| juniper:pulse_connect_secure | 7.1 |
| juniper:pulse_connect_secure | 7.4 |
| juniper:pulse_connect_secure | 8.0 |
| juniper:pulse_connect_secure | 8.1 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).