Debian LinuxOperating system · Debian
CVE-2012-1114
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 · uneditedA Cross-Site Scripting (XSS) vulnerability exists in LDAP Account Manager (LAM) Pro 3.6 in the filter parameter to cmd.php in an export and exporter_id action. and the filteruid parameter to list.php.
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 confidenceReflected XSS vulnerability in LDAP Account Manager Pro 3.6 where the 'filter' parameter to cmd.php (in export/exporter_id actions) and 'filteruid' parameter to list.php are not properly sanitized before being reflected in the HTTP response, allowing injection of malicious script content.
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
Debian LinuxOperating system
= 8.0= 9.0
FedoraOperating system
= 16= 17= 18= 3.6CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Identify installed LDAP Account Manager versionCheck the LAM version by reviewing version files in the installation directory, or by checking package management tools (dpkg/rpm) if installed via system packages. Common paths include /usr/share/lam/, /var/www/html/lam/, or the LAM Pro installation directory.Affected if The installed version is 3.6.x (specifically 3.6) as reported by the package manager or version file.
-
Locate vulnerable PHP script cmd.phpFind the cmd.php file in the LAM web directory - typically in the root LAM folder or under htdocs. Search for cmd.php and verify it handles the 'export' or 'exporter_id' actions.Affected if cmd.php exists in the LAM installation and the application is accessible via web.
-
Locate vulnerable PHP script list.phpFind the list.php file in the LAM web directory - typically in the root LAM folder or under htdocs. Verify it accepts the 'filteruid' parameter.Affected if list.php exists in the LAM installation and the application is accessible via web.
-
Confirm web interface is activeVerify the LAM web interface is running and accessible by attempting to reach the application URL (e.g., http://hostname/lam or similar path).Affected if The LAM web application is actively serving requests.
You are affected if LDAP Account Manager version 3.6 is installed and the web interface is accessible, as both cmd.php (filter parameter) and list.php (filteruid parameter) in this version contain the reflected XSS vulnerability.
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 dataApply proper input validation and output encoding to the filter and filteruid parameters in cmd.php and list.php respectively, or upgrade to the latest LAM version which should contain the fix.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1114 — 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-1114 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