Ltsp Display ManagerApplication · Canonical
CVE-2012-1166
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 default keybindings for wwm in LTSP Display Manager (ldm) 2.2.x before 2.2.7 allow remote attackers to execute arbitrary commands via the KP_RETURN keybinding, which launches a terminal window.
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 · high confidenceLTSP Display Manager (ldm) versions 2.2.x before 2.2.7 contains insecure default keybindings for the wwm window manager. The KP_RETURN (keypad enter) keybinding is configured to launch a terminal window by default, which can be exploited by remote attackers to execute arbitrary commands on the affected system.
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
Ltsp Display ManagerApplication
= 2.2.4= 2.2.5= 2.2.6
Ubuntu LinuxOperating system
= 11.04= 11.10CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Verify ldm versionRun 'ldm --version' or check the installed package version using your system's package manager (e.g., 'dpkg -l | grep ldm' on Debian/Ubuntu). Compare the version number to the affected range (2.2.4, 2.2.5, 2.2.6).Affected if The installed version is 2.2.4, 2.2.5, or 2.2.6.
-
Confirm wwm window manager is in useCheck if the wwm window manager is installed and active on the LTSP client. Look for wwm-related processes or configuration files in the LTSP environment.Affected if wwm is the active window manager in the LTSP setup.
-
Locate wwm keybinding configurationSearch for wwm configuration files in typical locations such as /etc/ldm/, /etc/wwm/, or within the user's configuration directory. Look for files named .wwmrc, wwmrc, or similar.Affected if A wwm configuration file exists and contains keybinding definitions.
-
Inspect KP_RETURN keybindingOpen the wwm configuration file and search for entries containing 'KP_RETURN' or 'keypad enter'. Examine whether this binding is set to launch a terminal or command execution.Affected if KP_RETURN is bound to a terminal or command launcher without additional restrictions.
You are affected if ldm version 2.2.4, 2.2.5, or 2.2.6 is installed AND the wwm window manager is in use with the default KP_RETURN keybinding that launches a terminal.
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.
dbcve · scopedUpgrade ldm to version 2.2.7 or later to receive the security patch. If immediate upgrade is not feasible, review and modify the default keybinding configuration to remove or restrict the KP_RETURN binding.
LTSP Display Manager 2.2.7
- Upgrade LTSP Display Manager (ldm) to version 2.2.7 or later
- After upgrading, verify the KP_RETURN keybinding no longer executes arbitrary commands
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ltsp Display Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1166 — 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-2012-1166 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