# CVE-2018-6316: Security feature bypass in n/a

> Authenticated low-privilege users can bypass application whitelisting in Ivanti Endpoint Security when the Application Control module is in lockdown mode.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmwq-hqgh-72q3

## What is CVE-2018-6316?

CVE-2018-6316 is a high-severity vulnerability in n/a, published on 15 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ivanti Endpoint Security (formerly HEAT Endpoint Management and Security Suite) 8.5 Update 1 and earlier allows an authenticated user with low privileges and access to the local network to bypass application whitelisting when using the Application Control module on Ivanti Endpoint Security in lockdown mode.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Ivanti Endpoint Security.

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

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

## Is CVE-2018-6316 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6316 is a high-severity vulnerability in n/a, published on 15 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6316 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-2018-6316/ (Markdown: https://insights.sbomify.com/CVE-2018-6316/index.md)
```

## Sources

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

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