# CVE-2017-7995: Information disclosure in n/a

> A flaw in Xen PV guests allowed host PCI device memory reads before permission checks, leading to information disclosure.

- **Severity:** Low 3.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **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:** 3 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-7995, GHSA-x43f-7h79-3278

## What is CVE-2017-7995?

CVE-2017-7995 is a low-severity vulnerability in Novell Suse Linux Enterprise Server, published on 3 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Xen PV guest before Xen 4.3 checked access permissions to MMIO ranges only after accessing them, allowing host PCI device space memory reads, leading to information disclosure. This is an error in the get_user function. NOTE: the upstream Xen Project considers versions before 4.5.x to be EOL.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 6 products.


Products: Novell Suse Linux Enterprise Point of Sale, Novell Suse Linux Enterprise Server, Suse Manager, Suse Manager Proxy, Suse Openstack Cloud, Xen Xen.

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

Product is end of life, replace it.

## Is CVE-2017-7995 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7995 is a low-severity vulnerability in Novell Suse Linux Enterprise Server, published on 3 May 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-7995 in the wild and no public exploit code.

Affected product: Novell Suse Linux Enterprise Server. 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-7995/ (Markdown: https://insights.sbomify.com/CVE-2017-7995/index.md)
```

## Sources

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

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