# CVE-2017-14319: Other in n/a

> A flaw in Xen's grant unmapping logic allows attackers to bypass security checks, potentially leading to privilege escalation or unauthorized data access.

- **Severity:** High 8.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-14319, DEBIAN-CVE-2017-14319, GHSA-j3wj-mf3m-r9xc, UBUNTU-CVE-2017-14319

## What is CVE-2017-14319?

CVE-2017-14319 is a high-severity vulnerability in Xen Xen, published on 12 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A grant unmapping issue was discovered in Xen through 4.9.x. When removing or replacing a grant mapping, the x86 PV specific path needs to make sure page table entries remain in sync with other accounting done. Although the identity of the page frame was validated correctly, neither the presence of the mapping nor page writability were taken into account.

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

It affects 1 product.


Products: Xen Xen.

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

Apply the vendor's patch.

## Is CVE-2017-14319 being exploited?

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

## Other vulnerabilities in Xen Xen

- [CVE-2017-10912](https://insights.sbomify.com/CVE-2017-10912/): Privilege escalation in n/a (critical 10.0)
- [CVE-2017-10918](https://insights.sbomify.com/CVE-2017-10918/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10920](https://insights.sbomify.com/CVE-2017-10920/): Memory corruption in n/a (critical 10.0)
- [CVE-2017-10921](https://insights.sbomify.com/CVE-2017-10921/): Memory corruption in n/a (critical 10.0)
- [CVE-2025-27466](https://insights.sbomify.com/CVE-2025-27466/): Mutiple vulnerabilities in the Viridian interface (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14319 is a high-severity vulnerability in Xen Xen, published on 12 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14319 in the wild and no public exploit code.

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

## Sources

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

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