# CVE-2014-3684: Missing authorization in n/a

> Authenticated users can kill arbitrary processes in TORQUE Resource Manager due to missing ownership validation, leading to privilege escalation or denial of service.

- **Severity:** Medium 6.8 (`AV:N/AC:L/Au:S/C:N/I:N/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:** Yes
- **Published:** 30 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DLA-78-1, DSA-3058-1, GHSA-8xjh-f37p-57cj, MGASA-2014-0408, UBUNTU-CVE-2014-3684

## What is CVE-2014-3684?

CVE-2014-3684 is a medium-severity missing authorization vulnerability in n/a, published on 30 Oct 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The tm_adopt function in lib/Libifl/tm.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 5.0.x, 4.5.x, 4.2.x, and earlier does not validate that the owner of the process also owns the adopted session id, which allows remote authenticated users to kill arbitrary processes via a crafted executable.

Weakness: CWE-264

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

It affects 1 product.


Products: Adaptivecomputing Torque Resource Manager.

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

Apply the vendor's patch.

## Is CVE-2014-3684 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0749](https://insights.sbomify.com/CVE-2014-0749/): Memory corruption in n/a (critical 10.0)
- [CVE-2013-4495](https://insights.sbomify.com/CVE-2013-4495/): Command injection in n/a (critical 10.0)
- [CVE-2013-4319](https://insights.sbomify.com/CVE-2013-4319/): Missing authorization in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3684 is a medium-severity missing authorization vulnerability in n/a, published on 30 Oct 2014. 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-3684 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-3684/ (Markdown: https://insights.sbomify.com/CVE-2014-3684/index.md)
```

## Sources

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

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