# CVE-2015-5369: Security feature bypass in n/a

> Remote attackers can bypass TLS validation to conduct man-in-the-middle attacks when Hardware Acceleration is enabled on Pulse Secure devices.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-26rc-pv36-f3pg

## What is CVE-2015-5369?

CVE-2015-5369 is a medium-severity vulnerability in n/a, published on 11 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation), CWE-17

## Which versions are affected by CVE-2015-5369?

It affects 1 product.


Products: Juniper Pulse Connect Secure.

## How do I fix CVE-2015-5369?

No fix has been published for CVE-2015-5369 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-5369 being exploited?

There is no known exploitation of CVE-2015-5369 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-7322](https://insights.sbomify.com/CVE-2015-7322/): Information disclosure in n/a (medium 5.0)
- [CVE-2015-7323](https://insights.sbomify.com/CVE-2015-7323/): Auth bypass in n/a (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5369 and fix it if it is affected.

What it is: CVE-2015-5369 is a medium-severity vulnerability in n/a, published on 11 Aug 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5369 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-5369/ (Markdown: https://insights.sbomify.com/CVE-2015-5369/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-5369
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-5369
- OSV: https://osv.dev/vulnerability/CVE-2015-5369

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-5369/
Summaries are generated and may contain mistakes; the official description above is the record.