dbcve.org
Security Directory IntegratorApplication · Ibm

CVE-2024-28770

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 does not set the secure attribute on authorization tokens or session cookies. Attackers may be able to get the cookie values by sending a http:// link to a user or by planting this link in a site the user goes to. The cookie will be sent to the insecure link and the attacker can then obtain the cookie value by snooping the traffic.

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 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 fail to set the 'Secure' flag on session cookies and authorization tokens. This allows cookies to be transmitted over unencrypted HTTP connections, enabling attackers to intercept them via man-in-the-middle or by enticing users to visit HTTP links.

MitigationConfigure the session cookies and authorization tokens to include the Secure attribute, ensuring they are only transmitted over HTTPS connections.

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
Security Verify Directory IntegratorApplication
Affected:= 10.0.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 product and version
    Locate the IBM Security Directory Integrator or IBM Security Verify Directory Integrator installation directory. Check the version file or product information (typically in conf/version.properties, about/dialog, or the installation manifest).
    Affected if The installed version is exactly 7.2.0 for IBM Security Directory Integrator or exactly 10.0.0 for IBM Security Verify Directory Integrator.
  2. Capture HTTP response headers from the login or authentication endpoint
    Access the application's login page or authentication interface over HTTP (http://hostname:port). Use a browser developer tool, curl -i, or a network capture tool to capture the Set-Cookie headers in the HTTP response.
    Affected if Set-Cookie headers are present for session cookies or authorization tokens without the Secure attribute.
  3. Verify cookie attributes in the HTTP response
    Examine the Set-Cookie header values for session-related cookies (look for sessionid, JSESSIONID, auth token, or similar session identifiers). Check whether the string 'Secure' appears in the cookie definition.
    Affected if Session cookies or authorization tokens are present in the HTTP response without the Secure flag (the cookie definition does not include '; Secure' or ';secure').
  4. Confirm the application is accessible over HTTP
    Attempt to access the application login or main page using http:// (not https://). Verify the server responds with content over an unencrypted connection.
    Affected if The application serves content over HTTP, allowing cookies to be transmitted in plaintext.
  5. Review cookie configuration in deployment descriptor or config files
    Check the application's configuration files (such as web.xml, ibmdi-config.xml, or similar deployment descriptors) for session cookie settings. Look for <session-config> or cookie-related parameters.
    Affected if Session cookie configuration lacks the secure attribute or is explicitly set to false.

You are affected if you are running exactly version 7.2.0 of IBM Security Directory Integrator or exactly version 10.0.0 of IBM Security Verify Directory Integrator and your application transmits session cookies or authorization tokens over HTTP without the Secure flag set.

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

Configure the session cookies and authorization tokens to include the Secure attribute, ensuring they are only transmitted over HTTPS connections.

Fix this in Security Directory Integrator Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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