dbcve.org
Tivoli Workload SchedulerApplication · Ibm

CVE-2022-22486

CRITICAL · 9.1 CVSS v3.1 Published 2023-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 Tivoli Workload Scheduler 9.4, 9.5, and 10.1 is vulnerable to an XML External Entity Injection (XXE) attack when processing XML data. A remote attacker could exploit this vulnerability to expose sensitive information or consume memory resources. IBM X-Force ID: 226328.

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 Tivoli Workload Scheduler versions 9.4, 9.5, and 10.1 contains an XML External Entity Injection (XXE) vulnerability when processing XML data. A remote attacker can exploit this by sending specially crafted XML requests to expose sensitive information from local files or consume memory resources leading to denial of service.

MitigationDisable external entity processing in XML parsers by disabling DTDs, disabling external entity resolution, and using a secure XML parser configuration. Apply IBM's official patch when available.

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
Tivoli Workload SchedulerApplication
Affected:= 9.4= 9.5= 10.1

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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 installed IBM Tivoli Workload Scheduler version
    Run the version check command for your TWS installation (typically 'twslsversion' or check installation logs, Readme files, or the product information panel in the admin console)
    Affected if The installed version is exactly 9.4, 9.5, or 10.1 (these are the exact versions affected, not version ranges)
  2. Locate XML processing components
    Identify processes or services that handle XML input within TWS. Common locations include job submission interfaces, scheduler configuration imports, or web service endpoints. Search for XML parser configurations in config files or application server settings.
    Affected if The product has XML processing functionality enabled and in use
  3. Verify network accessibility of XML-handling endpoints
    Check if TWS web interfaces, REST APIs, or other network-accessible endpoints that accept XML data are exposed. Review firewall rules and access controls around TWS ports (typically 31100, 31102, or custom ports for your installation).
    Affected if XML-processing endpoints are reachable over the network to untrusted users
  4. Inspect XML parser configuration
    Examine XML parser settings in TWS configuration files (commonly in conf/ or config directories under the TWS installation root). Look for parser configurations that allow external entity processing or DTD processing.
    Affected if XML parsers are configured to allow external entities or DTD processing (XXE requires this to exploit)
  5. Review audit logs for suspicious XML requests
    Check TWS audit and access logs for incoming requests containing XML payloads with entity references (look for patterns like '<!ENTITY', 'SYSTEM', 'PUBLIC' in request bodies or unusual file:// references in recent logs.
    Affected if There are recent XML requests containing potential XXE payload patterns

You are affected if you are running exactly version 9.4, 9.5, or 10.1 of IBM Tivoli Workload Scheduler and the product's XML processing features are accessible over the network with external entity processing enabled in the XML parser configuration.

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

Disable external entity processing in XML parsers by disabling DTDs, disabling external entity resolution, and using a secure XML parser configuration. Apply IBM's official patch when available.

Recommended fix Moderate confidence
  1. 1. Check the IBM Support portal for Tivoli Workload Scheduler security patches using CVE-2022-22486 or APAR IT40941
  2. 2. Apply the appropriate security patch for your version (9.4, 9.5, or 10.1) as provided by IBM
  3. 3. After patching, validate that XXE functionality is disabled in XML parser configuration
  4. 4. Test the XML processing functionality to ensure normal operations are not impacted
  5. 5. Monitor IBM security bulletins for any subsequent related patches

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

Fix this in Tivoli Workload Scheduler Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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