CVE-2006-7191
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 · uneditedUntrusted search path vulnerability in lamdaemon.pl in LDAP Account Manager (LAM) before 1.0.0 allows local users to gain privileges via a modified PATH that points to a malicious rm program.
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 confidenceLDAP Account Manager's lamdaemon.pl script before version 1.0.0 contains an untrusted search path vulnerability where the rm command is invoked without an absolute path, allowing a local attacker with controlled PATH environment variable to execute arbitrary code by placing a malicious rm binary earlier in the search path.
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<= 1.0_rc2CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Locate the lamdaemon.pl scriptSearch for the file lamdaemon.pl in your LDAP Account Manager installation directory, typically found in the 'lamdaemon' subdirectory or similar location within the LAM installation path.Affected if The script exists on the system and the installed LAM version is 1.0_rc2 or earlier.
-
Determine the installed LDAP Account Manager versionCheck the version information for your LDAP Account Manager installation, often found in a VERSION file, about page, or by checking the package/version metadata of your LAM installation.Affected if The installed version is 1.0_rc2 or any version lower than 1.0.0.
-
Inspect the lamdaemon.pl script for rm command usageOpen the lamdaemon.pl file in a text editor and search for instances where the 'rm' command is called without an absolute path (e.g., just 'rm' instead of '/bin/rm').Affected if The script contains calls to 'rm' or other system commands without specifying the full absolute path like '/bin/rm'.
-
Verify PATH environment variable handlingCheck if the lamdaemon.pl script is executed in an environment where the PATH environment variable could be influenced, or if the script relies on the system's PATH to locate the rm command.Affected if The script is run with a user-controlled or modifiable PATH environment variable, allowing an attacker to place a malicious executable earlier in the search order than the system rm.
You are affected if LDAP Account Manager version is 1.0_rc2 or lower, the lamdaemon.pl script exists on your system, and the script invokes rm without an absolute path while allowing a potentially controlled PATH variable during execution.
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 dataUpdate to LDAP Account Manager 1.0.0 or later, which includes the vendor patch; alternatively, modify the script to use absolute paths for system commands like /bin/rm.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-7191 — 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-2006-7191 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