CVE-2011-5275
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe install script for Domain Technologie Control (DTC) before version 0.34.1 misconfigures sudoers to grant the dtc user permission to execute the chrootuid command with elevated privileges. This allows local users with access to the dtc account to leverage chrootuid through sudo for privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.32.11= 0.24.6= 0.25.1= 0.25.2= 0.25.3= 0.26.7= 0.26.8= 0.26.9= 0.27.3= 0.28.2= 0.28.3= 0.28.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if DTC is installed on the systemLook for DTC-related processes, or check common package management systems (dpkg -l | grep dtc, rpm -qa | grep dtc)Affected if DTC is installed and running on the system
-
Determine the installed DTC versionCheck the DTC version using the package manager, or look for a version file in the DTC installation directoryAffected if The installed version matches one of the affected versions listed: <= 0.32.11, or any of 0.24.6, 0.25.1, 0.25.2, 0.25.3, 0.26.7, 0.26.8, 0.26.9, 0.27.3, 0.28.2, 0.28.3, 0.28.4
-
Verify the dtc system user existsCheck for the dtc user in /etc/passwd (grep ^dtc: /etc/passwd) or using the id command for dtcAffected if A dtc user account exists on the system
-
Inspect sudoers configuration for chrootuid permissionsReview the sudoers file (typically /etc/sudoers or files in /etc/sudoers.d/) for entries granting the dtc user permission to run chrootuid with sudo privilegesAffected if The sudoers configuration contains a line granting the dtc user permission to execute chrootuid via sudo (for example: dtc ALL=(ALL) NOPASSWD: /path/to/chrootuid)
If DTC is installed with an affected version AND the dtc user exists AND the sudoers configuration grants the dtc user permission to run chrootuid via sudo, then the system is vulnerable to privilege escalation via CVE-2011-5275.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade DTC to version 0.34.1 or later, or manually edit the sudoers configuration to remove the chrootuid permissions granted to the dtc user.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-5275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-5275 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data