Skip to main content
MediumContentOWASP A05:2021CWE-209

How to fix: LDAP Error Message Exposed

LDAP error message in response.

Why it matters

Reveals directory structure.

LDAP errors may expose user enumeration.

How to fix it

  1. 1Return generic error messages.

Code examples

Catch and mask LDAP errors

TypeScript
try {
  const result = await ldapClient.search(dn, opts);
  return Response.json(result);
} catch (err) {
  console.error("LDAP error:", err);
  return Response.json({ error: "Authentication failed" }, { status: 401 });
  // Never expose LDAP DNs, error codes, or server details to clients
}

References

Detected automatically by VulnRadar. The check id is ldap-error-exposed, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is LDAP Error Message Exposed?
VulnRadar rates this medium severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id ldap-error-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does LDAP Error Message Exposed map to?
It maps to CWE-209. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for ldap error message exposed

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: LDAP Error Message Exposed | VulnRadar