Automation Decision ServicesApplication · Ibm

CVE-2024-31906

MEDIUM · 6.2 CVSS v3.1 Published 2025-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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 Automation Decision Services 23.0.2 allows web pages to be stored locally which can be read by another user on the system.

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 Automation Decision Services 23.0.2 stores web pages in a local directory with insufficient access controls, allowing any user on the system to read files created by other users. This is a local information disclosure vulnerability stemming from improper file permission configuration on the application's web page storage location.

MitigationConfigure proper file system permissions on the web page storage directory to ensure only the owning user can read/write files, or relocate storage to a secured directory with appropriate access controls.

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
Automation Decision ServicesApplication
Affected:= 23.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Confirm IBM Automation Decision Services version
    Check installed version of IBM Automation Decision Services (look in installation directory, version manifest, or product-specific command). Compare to 23.0.2.
    Affected if Version is exactly 23.0.2
  2. Locate web page storage directory
    Identify the application's storage location for web pages (check application configuration files, documentation, or default installation paths for web content directories).
    Affected if Web page storage directory exists and is in use
  3. Inspect file permissions on storage directory
    Use file system commands (such as 'ls -la' on Unix or right-click Properties on Windows) to examine permissions on the identified web page storage directory.
    Affected if Directory permissions allow read access to users other than the file owner (e.g., world-readable, group-readable with broad group membership, or missing restrictive ACLs)
  4. Verify cross-user file access
    As a non-owner test user, attempt to read or list files in the web page storage directory created by another user.
    Affected if Non-owner users can read files they did not create in this directory

If IBM Automation Decision Services version 23.0.2 is installed AND the web page storage directory has overly permissive access controls allowing unauthorized users to read files created by others, the environment is affected by this vulnerability.

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

Configure proper file system permissions on the web page storage directory to ensure only the owning user can read/write files, or relocate storage to a secured directory with appropriate access controls.

Fix this in Automation Decision Services Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31906 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