dbcve.org
Rational Developer For IApplication · Ibm

CVE-2024-25050

HIGH · 7.8 CVSS v3.1 Published 2024-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 i 7.2, 7.3, 7.4, 7.5 and IBM Rational Development Studio for i 7.2, 7.3, 7.4, 7.5 networking and compiler infrastructure could allow a local user to gain elevated privileges due to an unqualified library call. A malicious actor could cause user-controlled code to run with administrator privileges. IBM X-Force ID: 283242.

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 i and Rational Development Studio for i contain a local privilege escalation vulnerability in the networking and compiler infrastructure. Attackers exploit an unqualified library call to load a malicious library with administrator privileges, achieving arbitrary code execution at elevated privilege levels.

MitigationApply IBM's security patches for CVE-2024-25050 to affected IBM i versions (7.2-7.5) and Rational Development Studio for i. Limit local system access to trusted administrators and monitor for unauthorized library loading.

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
Rational Developer For IApplication
Affected:= 7.2= 7.3= 7.4= 7.5
IOperating system
Affected:= 7.2= 7.3= 7.4= 7.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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Check IBM i operating system version
    Run command 'DSPSYSVAL QSS1MIC' or use 'WRKSYSVAL SYSBAS' to display system value QSS1MIC which shows the current IBM i release. Alternatively, use 'DSPOBJD OBJ(QSYS/QSYS) OBJTYPE(*LIB)' and check the attribute information.
    Affected if The displayed version is 7.2, 7.3, 7.4, or 7.5, indicating the IBM i system is running an affected version.
  2. Check Rational Development Studio for i installation and version
    On the IBM i command line, run 'WRKOBJPDG OBJ(QRDP*) OBJTYPE(*PGM)' or check the installed licensed programs using 'DSPSFWRSC' and look for entries containing 'Rational Developer for i' or product ID 5770RD1. Query the specific version using 'DSPDTAARA LIB(QTCP) DTAARA(*ALL)' if configured.
    Affected if Rational Development Studio for i is installed with version 7.2, 7.3, 7.4, or 7.5, placing the environment in the affected product range.
  3. Verify presence of vulnerable networking or compiler components
    Check for the presence of compiler-related libraries or programs in the system by running 'WRKOBJ OBJ(*ALL) OBJTYPE(*MODULE)' with library list entries for QRDARS, QRDC, or QRPGLESYS. Use 'DSPOBJD OBJ(*ALL/QRDARS*) OBJTYPE(*SRVPGM)' to list Rational compiler service programs.
    Affected if Networking or compiler infrastructure components from Rational Development Studio for i are present on the system, which contain the vulnerable unqualified library call mechanism.
  4. Inspect system for unauthorized or unexpected library files
    Use 'WRKOBJ OBJ(*ALL) OBJTYPE(*FILE) OBJATTR(*DLL)' to list dynamic link libraries on the system. Check directories such as /QOpenSys/usr/lib or QIBM/UserData for unexpected .so, .a, or .dll files that may have been placed by an attacker exploiting the library loading flaw.
    Affected if Unexpected or recently created library files exist in system library paths, which could indicate exploitation of the vulnerability to load malicious libraries.
  5. Review job logs for library loading warnings
    Examine system job logs using 'WRKJOB' or 'DSPJOBLOG' for jobs running under user profiles with *ALLOBJ special authority. Look for messages indicating failed or unqualified library lookups (message IDs like CPA3B04 or CPF3C2E) or attempts to load libraries from unexpected paths.
    Affected if Job logs show repeated unqualified library load attempts or warnings from compiler or networking jobs, suggesting the vulnerable code path is being exercised.

A system is affected if it runs IBM i or Rational Development Studio for i versions 7.2 through 7.5, with the compiler or networking components present and the vulnerable library loading mechanism exposed to local 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

Apply IBM's security patches for CVE-2024-25050 to affected IBM i versions (7.2-7.5) and Rational Development Studio for i. Limit local system access to trusted administrators and monitor for unauthorized library loading.

Recommended fix Moderate confidence

Apply IBM i and Rational Development Studio for i security PTFs; contact IBM support for specific PTF numbers

  1. Check IBM Support portal for the latest PTFs (Program Temporary Fixes) for IBM i and Rational Development Studio for i
  2. Apply the relevant security PTFs for CVE-2024-25050 (IBM X-Force ID: 283242)
  3. After applying PTFs, verify the fix by reviewing IBM's PTF cover letters for the security APAR
  4. Restart affected services as required by the PTF documentation
  5. Validate that unqualified library calls are now properly qualified with secure paths
Caveat PTFs for IBM i and Rational Development Studio for i typically require scheduled maintenance windows and may require system reboot

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

Fix this in Rational Developer For I Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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