# CVE-2014-0749: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in TORQUE Resource Manager due to improper handling of large count values.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2936-1, GHSA-vpg2-8g7f-3vh6, UBUNTU-CVE-2014-0749

## What is CVE-2014-0749?

CVE-2014-0749 is a critical memory corruption vulnerability in n/a, published on 16 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow in lib/Libdis/disrsi_.c in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 2.5.x through 2.5.13 allows remote attackers to execute arbitrary code via a large count value.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Adaptivecomputing Torque Resource Manager.

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

Apply the vendor's patch.

## Is CVE-2014-0749 being exploited?

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

Public exploit code:

- TORQUE Resource Manager 2.5.x < 2.5.13 - Stack Buffer Overflow Stub (exploitdb)

## Other vulnerabilities in n/a

- [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)
- [CVE-2014-3684](https://insights.sbomify.com/CVE-2014-3684/): Missing authorization in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0749 is a critical memory corruption vulnerability in n/a, published on 16 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0749 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-0749/ (Markdown: https://insights.sbomify.com/CVE-2014-0749/index.md)
```

## Sources

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

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