dbcve.org
Data Virtualization Manager For Z\/osApplication · Ibm

CVE-2024-52899

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 Data Virtualization Manager for z/OS 1.1 and 1.2 could allow an authenticated user to inject malicious JDBC URL parameters and execute code on the server.

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 Data Virtualization Manager for z/OS versions 1.1 and 1.2 contains a JDBC URL parameter injection vulnerability. An authenticated user can craft malicious JDBC URL parameters that are not properly validated or sanitized, allowing arbitrary code execution on the underlying z/OS server.

MitigationApply IBM's available patch or upgrade to a fixed version of Data Virtualization Manager for z/OS. If immediate patching is not possible, restrict database connection configuration privileges to only trusted administrators and implement additional input validation on JDBC connection parameters at the application layer.

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
Data Virtualization Manager For Z\/osApplication
Affected:= 1.1= 1.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 if IBM Data Virtualization Manager for z/OS is installed
    Check the installed product by querying the system for IBM Data Virtualization Manager for z/OS components. Use IBM system commands such as 'd m=*' or check the SMP/E distribution zone for the product. Look for records containing 'IBM Data Virtualization Manager' or 'DVZ' in the product name.
    Affected if The product is not installed on the system (not affected). If installed, continue to version check.
  2. Determine the installed version of Data Virtualization Manager for z/OS
    Execute IBM utility commands to display the product version, such as checking the CSIQS00 output, running 'modmap' against DVZ load modules, or reviewing SMP/E APPLY/ACCEPT output. Look for version indicators showing 1.1 or 1.2.
    Affected if The installed version is 1.1 or 1.2 (vulnerable). Versions outside this range are not affected by this specific CVE.
  3. Verify if JDBC connectivity is enabled or configured
    Examine the Data Virtualization Manager configuration datasets for JDBC-related configuration members. Check for JDBC data sources, connection pool definitions, or JDBC URL parameters in the DVZ configuration. Look for dataset names containing 'JDBC' or 'DSN' in the DVZ configuration library.
    Affected if JDBC connectivity is not configured or disabled (the vulnerability cannot be exploited). If JDBC is enabled and configured, the environment may be vulnerable.
  4. Check user access to JDBC connection configuration
    Review RACF or equivalent security product definitions for users with access to DVZ database connection configuration functions. Use 'RLIST' commands or equivalent to examine the DVZ profiles controlling who can create or modify JDBC connection strings.
    Affected if Untrusted or low-privileged authenticated users have ability to configure JDBC connections (potential exploit pathway exists). The vulnerability requires an authenticated user to submit malicious JDBC URL parameters.

The environment is affected only if IBM Data Virtualization Manager for z/OS version 1.1 or 1.2 is installed with JDBC connectivity enabled, and an authenticated user can configure JDBC connection parameters.

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 IBM's available patch or upgrade to a fixed version of Data Virtualization Manager for z/OS. If immediate patching is not possible, restrict database connection configuration privileges to only trusted administrators and implement additional input validation on JDBC connection parameters at the application layer.

Fix this in Data Virtualization Manager For Z\/os Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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