Safeguard
Vulnerability Analysis•

CVE-2022-33167: Low Missing HTTPOnly Flag in IBM Directory Integrator

CVE-2022-33167 is a missing HTTPOnly cookie flag in IBM Security Directory Integrator 7.2.0 and 10.0.0, scored 3.7. Apply the IBM fix packs.

Safeguard Security Team
3 min read

CVE-2022-33167 is a low severity flaw in IBM Security Directory Integrator 7.2.0 and Security Verify Directory Integrator 10.0.0, scored 3.7. A cookie is set without the HTTPOnly flag, which could expose its contents. IBM's fixes are 7.2.0-ISS-SDI-FP0009 and ibm-svdi-10.0.0.1, so apply the matching one.

What's affected

IBM lists IBM Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 as affected. The fix for 7.2.0 is 7.2.0-ISS-SDI-FP0009, which is an earlier fix pack than the one for the sibling issues. The fix for 10.0.0 is ibm-svdi-10.0.0.1. IBM lists no workarounds. The bulletin was first published on 24 July 2024, with X-Force ID 228587.

IBM scores it 3.7 with CVSS 3.0, with network vector, high attack complexity, no privileges, no user interaction and low confidentiality impact. NVD agrees at 3.7 Low.

IBM says a remote attacker could obtain sensitive information from the cookie because the HTTPOnly flag is not set. That flag stops scripts running in the browser from reading a cookie. Its absence matters only if another flaw lets script run in the page. The record's kev flag is false.

Because the fix pack numbers differ across the three IBM bulletins, install the latest one and you cover all three.

Weakness class per the record: CWE-1004, CWE-732.

How to check if you're exposed

Use the browser developer tools or curl to check how session cookies are set by the web console:

curl -sI https://sdi.example.com/ | grep -i set-cookie

Replace the host with your own. If a session cookie lacks HttpOnly, the flaw is present. After patching, run the same check again.

Also check the version and fix pack level of the installation against 7.2.0-ISS-SDI-FP0009 or ibm-svdi-10.0.0.1, or later.

What to do now

  1. Check cookie flags on the product's web consoles.
  2. Apply the latest fix pack, which covers this and the sibling IBM bulletins.
  3. Serve consoles over HTTPS only and enable the Secure flag where configurable.
  4. Add a content security policy at the reverse proxy if you use one.

Why it matters

The weakness classes in the record are sensitive cookie without HttpOnly (CWE-1004) and incorrect default permissions (CWE-732). Both relate to a cookie that script can read.

The impact is small on its own, which is why the score is 3.7. It becomes useful to an attacker in combination with a cross site scripting bug, where reading the session cookie would let them take over the session.

It is a cheap fix, and a reminder to check cookie attributes during any web application review.

Quick check

Why is the score so low?

The attack needs high complexity and gives only a low confidentiality impact. The missing flag helps an attacker only if script can already run in the page.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.