# CVE-2017-11319: Privilege escalation in n/a

> Authenticated users can escalate privileges by modifying access level permissions due to insufficient validation in Perspective ICM Investigation & Case.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/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:** 11 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-932v-9p4x-h52g

## What is CVE-2017-11319?

CVE-2017-11319 is a high-severity vulnerability in n/a, published on 11 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Perspective ICM Investigation & Case 5.1.1.16 allows remote authenticated users to modify access level permissions and consequently gain privileges by leveraging insufficient validation methods and missing cross server side checking mechanisms.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-11319?

It affects 1 product.


Products: Resolver Perspective.

## How do I fix CVE-2017-11319?

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

## Is CVE-2017-11319 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11319 exists.

Public exploit code:

- Perspective ICM Investigation & Case 5.1.1.16 - Privilege Escalation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11319 and fix it if it is affected.

What it is: CVE-2017-11319 is a high-severity vulnerability in n/a, published on 11 Dec 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11319 exists.

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-2017-11319/ (Markdown: https://insights.sbomify.com/CVE-2017-11319/index.md)
```

## Sources

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

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