dbcve.org
Workload SchedulerApplication · Ibm

CVE-2022-22369

HIGH · 7.1 CVSS v3.1 Published 2022-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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 Workload Scheduler 9.4 and 9.5 could allow a local user to overwrite key system files which would cause the system to crash. IBM X-Force ID: 221187.

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 Workload Scheduler 9.4 and 9.5 contains a local privilege escalation vulnerability where an authenticated local user can overwrite critical system files due to improper file permission controls, leading to system crash and denial of service.

MitigationApply vendor patches when available, review and restrict file system permissions on the scheduler directories and binaries to prevent unauthorized modification by non-privileged users, and follow least-privilege principles for user 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
Workload SchedulerApplication
Affected:= 9.4= 9.5

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 IBM Workload Scheduler installation
    Run 'lsitcl' or check common installation paths such as /opt/IBM/ or /opt/IBM/TWS/ to locate the installation directory. Look for directories named 'WorkloadScheduler', 'TWS', or similar IBM scheduling products.
    Affected if The installed version is IBM Workload Scheduler version 9.4 or 9.5 exactly.
  2. Determine installed version number
    Check the version of IBM Workload Scheduler by inspecting version files in the installation directory, or run the scheduler version command if available (such as 'composer version' or 'JobScheduler -version' from the installation bin directory).
    Affected if The version returned is 9.4 or 9.5.
  3. Locate scheduler directories and binaries
    Within the installation directory, identify the main subdirectories containing scheduler binaries, scripts, and configuration files. Common locations include 'bin', 'scripts', 'jobs', and configuration subdirectories.
    Affected if Scheduler directories and binaries exist on the system.
  4. Check file permissions on scheduler directories
    Use 'ls -la' on the main scheduler installation directory and subdirectories. Run 'ls -ld <directory>' on key directories to view owner, group, and permission bits (read/write/execute for owner, group, others).
    Affected if Directories show write permission for group or others (permissions containing 'w' in the group or other fields), indicating potentially weak permission controls.
  5. Verify write access on critical binaries and scripts
    Use 'ls -la' on scheduler binaries in the bin directory and critical scripts. Attempt to identify if non-privileged users have write access to executable files.
    Affected if Executable files show write permission for non-owner users (group or others have 'w' permission), allowing authenticated local users to modify them.
  6. Test for unauthorized write access
    As a non-privileged user (or using 'su' to a non-root test account), attempt to create or modify files in the scheduler installation directory to confirm the vulnerability exists.
    Affected if Non-privileged users can successfully write to scheduler directories, binaries, or configuration files.

A user is affected if IBM Workload Scheduler version 9.4 or 9.5 is installed AND file permissions allow authenticated non-privileged users to write to scheduler directories, binaries, or critical system files.

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

Apply vendor patches when available, review and restrict file system permissions on the scheduler directories and binaries to prevent unauthorized modification by non-privileged users, and follow least-privilege principles for user access.

Fix this in Workload Scheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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