# CVE-2018-6320: Other in n/a

> Attackers can bypass security controls by sending unvalidated Host headers to Pulse Secure PCS and PPS login interfaces.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-86rc-v7r8-8fwp

## What is CVE-2018-6320?

CVE-2018-6320 is a critical vulnerability in Ivanti Connect Secure, published on 6 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been discovered in login.cgi in Pulse Secure Pulse Connect Secure (PCS) 8.1RX before 8.1R12 and 8.3RX before 8.3R2 and Pulse Policy Secure (PPS) 5.2RX before 5.2R9 and 5.4RX before 5.4R2 wherein an http(s) Host header received from the browser is trusted without validation.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-6320?

It affects 3 products.


Products: Ivanti Connect Secure, Pulsesecure Pulse Connect Secure, Pulsesecure Pulse Policy Secure.

## How do I fix CVE-2018-6320?

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

## Is CVE-2018-6320 being exploited?

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

## Other vulnerabilities in Ivanti Connect Secure

- [CVE-2021-22893](https://insights.sbomify.com/CVE-2021-22893/): Ivanti Pulse Connect Secure Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2019-11510](https://insights.sbomify.com/CVE-2019-11510/): Ivanti Pulse Connect Secure Arbitrary File Read (critical 9.9, exploited in the wild)
- [CVE-2024-21887](https://insights.sbomify.com/CVE-2024-21887/): Ivanti Connect Secure and Policy Secure Command Injection (critical 9.1, exploited in the wild)
- [CVE-2025-22457](https://insights.sbomify.com/CVE-2025-22457/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)
- [CVE-2025-0282](https://insights.sbomify.com/CVE-2025-0282/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6320 and fix it if it is affected.

What it is: CVE-2018-6320 is a critical vulnerability in Ivanti Connect Secure, published on 6 Sep 2018. 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-2018-6320 in the wild and no public exploit code.

Affected product: Ivanti Connect Secure. 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-2018-6320/ (Markdown: https://insights.sbomify.com/CVE-2018-6320/index.md)
```

## Sources

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

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