dbcve.org
Ldap Account ManagerApplication

CVE-2024-23333

MEDIUM · 6.6 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 8.7 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
LDAP Account Manager (LAM) is a webfrontend for managing entries stored in an LDAP directory. LAM's log configuration allows to specify arbitrary paths for log files. Prior to version 8.7, an attacker could exploit this by creating a PHP file and cause LAM to log some PHP code to this file. When the file is then accessed via web the code would be executed. The issue is mitigated by the following: An attacker needs to know LAM's master configuration password to be able to change the main settings; and the webserver needs write access to a directory that is accessible via web. LAM itself does not provide any such directories. The issue has been fixed in 8.7. As a workaround, limit access to LAM configuration pages to authorized users.

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 confidence

LDAP Account Manager versions before 8.7 allow arbitrary path specification in log configuration. An attacker with the master password can configure log files to point to web-accessible directories, then inject PHP code into logs which executes when accessed via web browser, achieving remote code execution.

MitigationUpgrade to LAM 8.7 or later. As a workaround, strictly limit access to LAM configuration pages to authorized users and ensure no writable directories exist within the web root.

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
Ldap Account ManagerApplication
Affected:< 8.7

CVSS 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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed LAM version
    Access the LAM administration interface and check the version number typically displayed on the login page or in the 'Help > About' section, or inspect the version file in the LAM installation directory if accessible
    Affected if The displayed version is before 8.7 (e.g., 8.6, 8.5, earlier releases)
  2. Verify master password configuration
    Attempt to access the LAM configuration area (usually at /lam/config/ or /config.php) and check if the master password is set or still at default
    Affected if The master password is not set, is left at default value, or is accessible to unauthorized users
  3. Review log file path settings
    In LAM configuration, navigate to 'Log Settings' or similar log configuration options and inspect the configured log file path
    Affected if The log file path is set to a location within the web server document root (e.g., /var/www/html/, /var/www/lam/, or any path accessible via HTTP/HTTPS)
  4. Check for writable web root directories
    Inspect the web server document root where LAM is hosted and identify any writable subdirectories accessible via the web server
    Affected if There exists a writable directory within the web-accessible path that could be targeted for log file placement

You are affected if LAM version is below 8.7 AND an attacker can access the configuration to set log paths to web-accessible directories, which would enable remote code execution via log poisoning.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.7 or later
Fixed in 8.7
Interim mitigation

Upgrade to LAM 8.7 or later. As a workaround, strictly limit access to LAM configuration pages to authorized users and ensure no writable directories exist within the web root.

Recommended fix High confidence

8.7

  1. Upgrade LDAP Account Manager to version 8.7 or later
  2. Verify the upgrade was successful by checking the LAM version in the web interface
  3. Ensure the master configuration password is strong and changed regularly
  4. Ensure the webserver does not have writable directories that are accessible via web
  5. As an additional precaution, restrict access to LAM configuration pages to authorized users only

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ldap Account Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23333 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23333 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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