dbcve.org
Workload SchedulerApplication · Ibm

CVE-2024-49351

MEDIUM · 5.5 CVSS v3.1 Published 2024-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/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.5, 10.1, and 10.2 stores user credentials in plain text which can be read by a local user.

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 versions 9.5, 10.1, and 10.2 stores user credentials in plain text within configuration files or other storage locations accessible to local filesystem users. A local attacker with read access to these files can obtain sensitive credentials in cleartext form.

MitigationUpgrade to a patched version of IBM Workload Scheduler that implements proper credential encryption, or restrict filesystem permissions on credential storage locations to prevent unauthorized local 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.5= 10.1= 10.2

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

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IBM Workload Scheduler installation and version
    Run command to locate the product installation (e.g., 'find /opt -name "*TWS*" -o -name "*Workload*"' or check installed packages) and determine the exact version number
    Affected if Version is 9.5, 10.1, or 10.2 exactly as listed in affected versions
  2. Locate credential storage locations
    Search for configuration directories typically used by IBM Workload Scheduler (commonly under installation root, look for 'config', 'conf', or 'security' subdirectories)
    Affected if Product is installed and configuration directories exist
  3. Find credential-containing configuration files
    Search for files that may contain credentials using common patterns: '*password*', '*credential*', '*security*', '*user*', '*.properties', '*.xml', '*.config' within the product directories
    Affected if Such configuration files exist in the product installation
  4. Inspect for plaintext credentials
    Examine identified configuration files for unencrypted password fields, plaintext user credentials, or API keys (use 'grep -i password' or 'cat' on suspected files)
    Affected if Credentials appear in cleartext form rather than being encrypted, hashed, or masked
  5. Verify filesystem permissions on credential files
    Check file permissions on credential-containing configuration files (ls -la) to determine if unauthorized local users could read them
    Affected if Files are readable by users other than the product owner or root

User is affected if IBM Workload Scheduler version 9.5, 10.1, or 10.2 is installed AND plaintext credentials are found in configuration files accessible to local filesystem users.

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

Upgrade to a patched version of IBM Workload Scheduler that implements proper credential encryption, or restrict filesystem permissions on credential storage locations to prevent unauthorized local access.

Recommended fix Moderate confidence

IBM Workload Scheduler fixed release (contact IBM Support for specific version as fixes are released per version)

  1. IBM Workload Scheduler stores user credentials in plain text, which is a security vulnerability. Obtain the appropriate security update or upgrade from IBM Support portal based on your specific version (9.5, 10.1, or 10.2).
  2. Apply the IBM interim fix (APAR) or upgrade to the fixed release level as specified in the IBM security bulletin.
  3. After applying the fix, verify that credentials are no longer stored in plaintext and are properly hashed/encrypted.
  4. Test the Workload Scheduler functionality to ensure the security update does not impact normal operations.
Caveat Verify with IBM that the security patch does not affect existing credential configurations or authentication workflows

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

Fix this in Workload Scheduler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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