# CVE-2017-3276: Privilege escalation in Solaris Operating System

> A high-privileged attacker can modify critical data or cause a denial of service in Solaris Kernel Zones via the virtualized block driver.

- **Severity:** Medium 5.7 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2017
- **Updated:** 9 Oct 2024
- **Also known as:** GHSA-xfrc-3x4c-8gwv

## What is CVE-2017-3276?

CVE-2017-3276 is a medium-severity vulnerability in Oracle Solaris, published on 27 Jan 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Solaris component of Oracle Sun Systems Products Suite (subcomponent: Kernel Zones virtualized block driver). The supported version that is affected is 11.3. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where Solaris executes to compromise Solaris. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Solaris accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Solaris. CVSS v3.0 Base Score 5.7 (Integrity and Availability impacts).

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

It affects 1 product.


Products: Oracle Solaris.

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

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

## Is CVE-2017-3276 being exploited?

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

## Other vulnerabilities in Oracle Solaris

- [CVE-2020-14871](https://insights.sbomify.com/CVE-2020-14871/): Oracle Solaris and Zettabyte File System (ZFS) Unspecified (critical 10.0, exploited in the wild)
- [CVE-2019-3010](https://insights.sbomify.com/CVE-2019-3010/): Oracle Solaris Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2026-46978](https://insights.sbomify.com/CVE-2026-46978/): Missing authorization in Oracle Solaris (critical 10.0)
- [CVE-2017-3623](https://insights.sbomify.com/CVE-2017-3623/): Other in Solaris Operating System (critical 10.0)
- [CVE-2014-0397](https://insights.sbomify.com/CVE-2014-0397/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3276 is a medium-severity vulnerability in Oracle Solaris, published on 27 Jan 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-3276 in the wild and no public exploit code.

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

## Sources

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

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