dbcve.org
Control DeskApplication · Ibm

CVE-2022-22330

MEDIUM · 5.3 CVSS v3.1 Published 2022-09-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Control Desk 7.6.1 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: 219126.

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 · moderate confidence

IBM Control Desk 7.6.1 fails to set the HTTPOnly flag on session cookies, allowing JavaScript access to sensitive cookie data. An attacker who can inject malicious scripts (e.g., via XSS) can steal session cookies and potentially hijack user sessions.

MitigationConfigure the web application server or IBM Control Desk to set the HTTPOnly attribute on all sensitive cookies, particularly session cookies, to prevent client-side script access.

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
Control DeskApplication
Affected:= 7.6.0= 7.6.0.1= 7.6.1= 7.6.1.1= 7.6.1.2= 7.6.1.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. Check IBM Control Desk version
    Access the IBM Control Desk About page via the web interface (typically at /maximo/webclient/login/about.jsp) or check the installation directory for version files. Alternatively, run: cat <install_dir>/maximoEAR.ear/META-INF/MANIFEST.MF | grep Implementation-Version
    Affected if The installed version matches 7.6.0, 7.6.0.1, 7.6.1, 7.6.1.1, 7.6.1.2, or 7.6.1.3 from the affected versions list
  2. Inspect session cookie headers
    Log into IBM Control Desk and open browser developer tools (F12). Go to the Network tab, refresh the page, and click on any authenticated request. Examine the Response Headers for Set-Cookie directives. Look for the session cookie (typically named JSESSIONID, MAXAUTH, or similar) and check if the HTTPOnly attribute is present.
    Affected if The Set-Cookie response headers for session cookies do NOT contain the HttpOnly attribute (the cookie is vulnerable to JavaScript access)
  3. Verify cookie accessibility via JavaScript
    While logged into IBM Control Desk, open the browser console and execute: document.cookie. Examine the output to see if session-related cookies (JSESSIONID, MAXAUTH, etc.) are visible.
    Affected if Session cookies appear in document.cookie output, confirming they are accessible to JavaScript and HTTPOnly is not set

You are affected if your IBM Control Desk version is 7.6.0 through 7.6.1.3 AND session cookies lack the HTTPOnly flag, allowing JavaScript to access them.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the web application server or IBM Control Desk to set the HTTPOnly attribute on all sensitive cookies, particularly session cookies, to prevent client-side script access.

Recommended fix Moderate confidence

IBM Control Desk 7.6.1.2 or later fixed release (check IBM Fix Central for specific APAR and download)

  1. 1. Check IBM Fix Central for the security patch for CVE-2022-22330 (IBM X-Force ID: 219126)
  2. 2. Download the applicable interim fix or fix pack for your IBM Control Desk version
  3. 3. Back up your current IBM Control Desk configuration and database
  4. 4. Apply the security fix following IBM's installation instructions
  5. 5. Verify that HTTPOnly flag is now set on session cookies by inspecting Set-Cookie headers
  6. 6. Test critical authentication flows to ensure functionality is not impacted
Caveat Review IBM's fix documentation for any configuration changes or prerequisites required before applying the patch

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

Fix this in Control Desk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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