CVE-2022-33167
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 · uneditedIBM Security Directory Integrator 7.2.0 and IBM Security Verify Directory Integrator 10.0.0 could allow a remote attacker to obtain sensitive information, caused by the failure to set the HTTPOnly flag. A remote attacker could exploit this vulnerability to obtain sensitive information from the cookie. IBM X-Force ID: 228587.
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 confidenceIBM Security Directory Integrator versions 7.2.0 and 10.0.0 fail to set the HTTPOnly flag on sensitive cookies, allowing client-side scripts to access cookie values. This enables attackers to potentially steal session credentials or other sensitive data via cross-site scripting (XSS) attacks or malicious JavaScript injection.
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= 7.2.0= 10.0.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed IBM Security Directory Integrator versionLocate the product installation directory and check the version information file or use the product's version command (typically found in the installation bin directory or in product documentation). Compare the version number to 7.2.0 or 10.0.0.Affected if The installed version is exactly 7.2.0 or 10.0.0 of IBM Security Directory Integrator or IBM Security Verify Directory Integrator.
-
Verify if HTTPOnly flag is present on authentication cookiesLog into the application and use browser developer tools (Application or Storage tab) or a proxy tool to inspect cookies set by the application. Look for cookies related to authentication, session, or login. Check the attributes column for the HTTPOnly flag.Affected if Sensitive cookies (authentication, session, or login-related) are present without the HTTPOnly flag set.
-
Capture and analyze HTTP response headers for Set-Cookie directivesUse a web proxy or browser network inspection to capture HTTP responses from the application. Examine Set-Cookie headers to see if the HttpOnly attribute is included when setting session or authentication cookies.Affected if Set-Cookie headers for sensitive cookies do not include the HttpOnly attribute.
-
Review application server or product configuration for cookie settingsCheck the application configuration files (such as web.xml, server configuration, or product-specific config files in the installation directory) for cookie-related settings. Look for configurations that control the HttpOnly or Secure flags on cookies.Affected if Cookie configuration explicitly disables HTTPOnly or does not specify it for sensitive cookies.
You are affected if your environment runs IBM Security Directory Integrator version 7.2.0 or IBM Security Verify Directory Integrator version 10.0.0, AND sensitive cookies are being set without the HTTPOnly flag.
Generated from the published advisory. Verify against your own configuration.
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 dataConfigure the affected application to set the HTTPOnly flag on all sensitive cookies, particularly authentication and session cookies. This is typically done at the application server level or in the code that sets the cookies.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33167 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-33167 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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