# CVE-2011-5275: Privilege escalation in n/a

> The DTC install script grants excessive sudo permissions to the dtc user, allowing local attackers to escalate privileges.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2014
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-564f-gcfr-5xx9

## What is CVE-2011-5275?

CVE-2011-5275 is a high-severity vulnerability in n/a, published on 20 Mar 2014. 

### Official description

The install script in Domain Technologie Control (DTC) before 0.34.1 gives sudo permissions for chrootuid to the dtc user, which makes it easier for context-dependent users to gain privileges.

Weakness: CWE-264

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

It affects 1 product.


Products: Gplhost Domain Technologie Control.

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

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

## Is CVE-2011-5275 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-5274](https://insights.sbomify.com/CVE-2011-5274/): Command injection in n/a (high 7.5)
- [CVE-2011-0434](https://insights.sbomify.com/CVE-2011-0434/): SQL injection in n/a (high 7.5)
- [CVE-2009-0402](https://insights.sbomify.com/CVE-2009-0402/): SQL injection in n/a (high 7.5)
- [CVE-2011-3195](https://insights.sbomify.com/CVE-2011-3195/): Command injection in n/a (medium 6.5)
- [CVE-2011-3197](https://insights.sbomify.com/CVE-2011-3197/): SQL injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-5275 is a high-severity vulnerability in n/a, published on 20 Mar 2014. 
Exploitation: There is no known exploitation of CVE-2011-5275 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-5275/ (Markdown: https://insights.sbomify.com/CVE-2011-5275/index.md)
```

## Sources

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

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