CVE-2011-5275 Privilege escalation in n/a
High 7.5
Published
Updated
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)
The DTC install script grants excessive sudo permissions to the dtc user, allowing local attackers to escalate privileges.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
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 include 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
Sources
Also known as GHSA-564f-gcfr-5xx9.