# CVE-2014-9768: Privilege escalation in n/a

> Authenticated users can escalate privileges by manipulating transaction codes, though vendor states security controls mitigate this risk.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qc8h-m9cf-7w7r

## What is CVE-2014-9768?

CVE-2014-9768 is a high-severity vulnerability in n/a, published on 18 Mar 2016. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Tivoli NetView Access Services (NVAS) allows remote authenticated users to gain privileges by entering the ADM command and modifying a "page ID" field to the EMSPG2 transaction code.  NOTE: the vendor's perspective is that configuration and use of available security controls in the NVAS product mitigates the reported vulnerability

Weakness: CWE-264

## Which versions are affected by CVE-2014-9768?

It affects 1 product.


Products: Ibm Tivoli Netview Access Services.

## How do I fix CVE-2014-9768?

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

## Is CVE-2014-9768 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9768 and fix it if it is affected.

What it is: CVE-2014-9768 is a high-severity vulnerability in n/a, published on 18 Mar 2016. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-9768 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-2014-9768/ (Markdown: https://insights.sbomify.com/CVE-2014-9768/index.md)
```

## Sources

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

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