dbcve.org
Security Directory IntegratorApplication · Ibm

CVE-2024-28765

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 7.2.0.15 / 10.0.0.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
IBM SDI 7.2.0.0 through 7.2.0.14 and IBM Security Directory Integrator 10.0.0.0 through 10.0.0.2 could allow a remote attacker to obtain sensitive information when a detailed technical error message is returned in the browser. This information could be used in further attacks against the system.

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

IBM Security Directory Integrator versions 7.2.0.0-7.2.0.14 and 10.0.0.0-10.0.0.2 return detailed technical error messages directly to the browser, exposing sensitive system information such as stack traces, file paths, database details, or configuration data that could aid attackers in reconnaissance and further exploitation.

MitigationConfigure the application to use custom error pages that return generic error messages without exposing technical details. Review and disable verbose error reporting in the web container configuration.

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
Security Directory IntegratorApplication
Affected:>= 7.2.0, < 7.2.0.15>= 10.0.0, < 10.0.0.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

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

  1. Identify the installed IBM Security Directory Integrator version
    Check the product version through the Administration Console, about page, or version file in the installation directory. Common locations include the 'about' section in the web UI or a version.properties file in the installation root.
    Affected if The installed version falls within 7.2.0.0-7.2.0.14 or 10.0.0.0-10.0.0.2, meaning it is lower than 7.2.0.15 or 10.0.0.3 respectively.
  2. Verify the web-based administration interface is accessible
    Confirm that the IBM Security Directory Integrator web console or administration portal is running and reachable on its configured port (typically 8080, 8443, or custom).
    Affected if The web interface is exposed and accessible, which is required for the error message disclosure to occur.
  3. Trigger a deliberate error condition to observe response
    Submit an invalid request to the web interface, such as a malformed input, missing required parameters, or access a non-existent resource. Observe the HTTP response body and any error pages returned.
    Affected if The response contains detailed technical information such as stack traces, file paths, database connection strings, configuration details, or Java exception messages rather than a generic error page.
  4. Review web container error handling configuration
    Examine the web container configuration files (such as web.xml) for error-page mappings. Check if custom error handlers are defined to return generic messages, or if verbose error reporting is enabled.
    Affected if No custom error pages are configured, or the container is set to display verbose error details (such as stack traces) to client browsers.

You are affected if the installed version is 7.2.0.0-7.2.0.14 or 10.0.0.0-10.0.0.2 AND the web interface returns detailed technical error messages to users instead of generic error pages.

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 7.2.0.15 / 10.0.0.3 or later
Fixed in 7.2.0.1510.0.0.3
Interim mitigation

Configure the application to use custom error pages that return generic error messages without exposing technical details. Review and disable verbose error reporting in the web container configuration.

Recommended fix High confidence

IBM Security Directory Integrator 7.2.0.15 (for 7.2.x branch) or 10.0.0.3 (for 10.0.x branch)

  1. 1. Identify the current version of IBM Security Directory Integrator installed in your environment.
  2. 2. Determine which branch (7.2.x or 10.0.x) is currently in use.
  3. 3. Download the corresponding fixed release: IBM Security Directory Integrator 7.2.0.15 (for 7.2.x users) or 10.0.0.3 (for 10.0.x users).
  4. 4. Obtain the download from IBM Fix Central or your authorized IBM support channel.
  5. 5. Review IBM's release notes and installation instructions for the specific version.
  6. 6. Test the upgrade in a non-production environment before deploying to production.
  7. 7. Apply the upgrade following IBM's standard upgrade procedures for Security Directory Integrator.
  8. 8. Verify that the fix is applied by confirming the version number and testing that detailed error messages are no longer exposed.

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

Fix this in Security Directory Integrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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