# CVE-2011-2193: Memory corruption in n/a

> Remote authenticated users can gain privileges via buffer overflows in TORQUE Resource Manager, requiring an upgrade to secure the system.

- **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:** Yes
- **Published:** 24 Jun 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DSA-2329-1, GHSA-7222-82wf-3qpq

## What is CVE-2011-2193?

CVE-2011-2193 is a high-severity memory corruption vulnerability in n/a, published on 24 Jun 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple buffer overflows in Terascale Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) 2.x before 2.4.14, 2.5.x before 2.5.6, and 3.x before 3.0.2 allow (1) remote authenticated users to gain privileges via a long Job_Name field in a qsub command to the server, and might allow (2) local users to gain privileges via vectors involving a long host variable in pbs_iff.

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

## Which versions are affected by CVE-2011-2193?

It affects 1 product.


Products: Clusterresources Torque Resource Manager.

## How do I fix CVE-2011-2193?

Upgrade to a fixed version.

## Is CVE-2011-2193 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2907](https://insights.sbomify.com/CVE-2011-2907/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2193 and fix it if it is affected.

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

## Sources

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

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