dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2024-12510

MEDIUM · 6.7 CVSS v3.1 Published 2025-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
If LDAP settings are accessed, authentication could be redirected to another server, potentially exposing credentials. This requires admin access and an active LDAP setup.

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 confidence

LDAP authentication settings can be manipulated to redirect authentication requests to an arbitrary server, causing user credentials to be sent to an attacker-controlled LDAP server. This is a configuration-level vulnerability where the LDAP server endpoint is not properly validated or restricted.

MitigationRestrict admin access to LDAP settings, implement server-side validation of LDAP endpoints, enable certificate validation for LDAP connections, and add alerts for configuration changes to LDAP settings.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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 if LDAP authentication is enabled
    Locate the authentication settings panel or configuration file in your application/system where LDAP authentication options are present. Look for settings named 'LDAP', 'Active Directory', 'Directory Services', or similar.
    Affected if LDAP authentication is enabled and configurable by users with access to authentication settings
  2. Locate the LDAP server endpoint configuration
    Find the setting that defines the LDAP server address - typically labeled as 'LDAP Server', 'Directory Server', 'LDAP URL', or 'Base DN'. This is often in the format ldap://hostname:port or ldaps://hostname:port.
    Affected if A configurable LDAP server endpoint setting exists that accepts user input or allows modification
  3. Inspect the configured LDAP server address
    Read the current value of the LDAP server endpoint setting. Verify whether it points to a legitimate internal directory server or an external/untrusted hostname or IP address.
    Affected if The LDAP endpoint points to a server outside your organization or to an untrusted/unknown hostname/IP
  4. Check if endpoint validation or restriction exists
    Look for settings that restrict which LDAP servers can be configured, such as whitelist/blacklist options, allowed domain lists, or server validation checks. Examine if the application validates the LDAP endpoint before saving.
    Affected if No validation mechanism exists to restrict the LDAP server endpoint to approved servers, or any arbitrary server can be configured
  5. Verify TLS certificate validation is enabled for LDAP
    Check if there is a setting to enable certificate validation or TLS verification for LDAP connections. Confirm it is turned on if your LDAP server uses SSL/TLS.
    Affected if Certificate validation for LDAP connections is disabled or not enforced
  6. Review configuration change logging and alerting
    Check if the system logs changes to LDAP authentication settings and provides alerts when the LDAP server endpoint is modified.
    Affected if No logging or alerting exists for changes to LDAP configuration settings

Your environment is affected if LDAP authentication is enabled with a configurable endpoint that can be set to an arbitrary server without validation, restriction, or change monitoring.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict admin access to LDAP settings, implement server-side validation of LDAP endpoints, enable certificate validation for LDAP connections, and add alerts for configuration changes to LDAP settings.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12510 — 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-12510 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