CVE-2015-5369Not scoredCWE-20

CVE-2015-5369: Juniper Pulse Connect Secure vulnerability

Juniper · Pulse Connect Secure

Affected: Juniper Pulse Connect Secure · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.8%probability of exploitation in the next 30 days

78th percentile

050100

Higher than 78% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Input Validation · Input Validation and Logic
Vendor: Juniper
Published: August 2015
Band: Possible (1 to 10%), August 2015

CoverageNo articles yet

No CyberSIXT article names CVE-2015-5369 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.