# CVE-2013-6306: Privilege escalation in n/a

> Local attackers can escalate privileges to Service Processor level on IBM Power 7 Systems via unspecified vectors.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 22 Aug 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vwfj-gpqr-5pqc

## What is CVE-2013-6306?

CVE-2013-6306 is a medium-severity vulnerability in n/a, published on 22 Aug 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability on IBM Power 7 Systems 740 before 740.70 01Ax740_121, 760 before 760.40 Ax760_078, and 770 before 770.30 01Ax770_062 allows local users to gain Service Processor privileges via unknown vectors.

## Which versions are affected by CVE-2013-6306?

It affects 15 products.


Products: Ibm Power 710, Ibm Power 720, Ibm Power 730, Ibm Power 740, Ibm Power 740 Firmware, Ibm Power 750, Ibm Power 760, Ibm Power 760 Firmware, Ibm Power 770, Ibm Power 770 Firmware, Ibm Power 780, Ibm Power 795, Ibm Power Ese, Ibm Powerlinux 7r1, Ibm Powerlinux 7r2.

## How do I fix CVE-2013-6306?

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

## Is CVE-2013-6306 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6306 and fix it if it is affected.

What it is: CVE-2013-6306 is a medium-severity vulnerability in n/a, published on 22 Aug 2014. 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-2013-6306 in the wild and no public exploit code.

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

## Sources

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

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