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

> Authenticated users with Take Action authority can bypass restrictions to execute arbitrary commands on IBM Tivoli Monitoring servers.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **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:** 2 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3qcc-hgxf-jmc5

## What is CVE-2014-6141?

CVE-2014-6141 is a high-severity vulnerability in n/a, published on 2 Feb 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Tivoli Monitoring (ITM) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, 6.2.3 through FP05, and 6.3.0 before FP04 allows remote authenticated users to bypass intended access restrictions and execute arbitrary commands by leveraging Take Action view authority to modify in-progress commands.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Tivoli Monitoring.

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

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

## Is CVE-2014-6141 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7411](https://insights.sbomify.com/CVE-2015-7411/): Privilege escalation in n/a (critical 9.9)
- [CVE-2025-3357](https://insights.sbomify.com/CVE-2025-3357/): IBM Tivoli Monitoring code execution (critical 9.8)
- [CVE-2017-1789](https://insights.sbomify.com/CVE-2017-1789/): Code injection in Tivoli Monitoring V6 (critical 9.8)
- [CVE-2025-3356](https://insights.sbomify.com/CVE-2025-3356/): IBM Tivoli Monitoring is vulnerable to unauthenticated file read and write operations (high 8.6)
- [CVE-2015-5003](https://insights.sbomify.com/CVE-2015-5003/): Command injection in n/a (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-6141 is a high-severity vulnerability in n/a, published on 2 Feb 2015. 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-6141 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-6141/ (Markdown: https://insights.sbomify.com/CVE-2014-6141/index.md)
```

## Sources

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

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