# CVE-2016-0263: Privilege escalation in n/a

> Local attackers can exploit a crafted command in IBM Spectrum Scale to gain elevated privileges or cause a denial of service.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hr33-v88j-j7w2

## What is CVE-2016-0263?

CVE-2016-0263 is a high-severity vulnerability in Ibm Spectrum Scale, published on 29 Jun 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Spectrum Scale 4.1 before 4.1.1.5 and 4.2 before 4.2.0.2 and General Parallel File System 3.5 before 3.5.0.30 allow local users to gain privileges or cause a denial of service via a crafted mmapplypolicy command.

Weakness: CWE-264

## Which versions are affected by CVE-2016-0263?

It affects 2 products.


Products: Ibm General Parallel File System Storage Server, Ibm Spectrum Scale.

## How do I fix CVE-2016-0263?

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

## Is CVE-2016-0263 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0263 and fix it if it is affected.

What it is: CVE-2016-0263 is a high-severity vulnerability in Ibm Spectrum Scale, published on 29 Jun 2016. 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-2016-0263 in the wild and no public exploit code.

Affected product: Ibm Spectrum Scale. 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-2016-0263/ (Markdown: https://insights.sbomify.com/CVE-2016-0263/index.md)
```

## Sources

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

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