IApplication · Ibm

CVE-2023-42006

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-01
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 Administration Runtime Expert for i 7.2, 7.3, 7.4, and 7.5 could allow a local user to obtain sensitive information caused by improper authority checks. IBM X-Force ID: 265266.

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 Administration Runtime Expert for i versions 7.2-7.5 contains improper authority checks that allow a local authenticated user to access sensitive information they should not have permission to view. This is a local privilege escalation/information disclosure vulnerability where the application fails to properly validate user authorization before disclosing data.

MitigationApply IBM's security patch for CVE-2023-42006 when available. Until then, limit local access to the IBM i system to trusted users only and follow least-privilege principles for user authorities.

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
IApplication
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
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. Verify IBM Administration Runtime Expert for i is installed
    On the IBM i system, use the 'Work with Software Resources' command (DSPSFWRSC) or 'Work with Licensed Programs' (WRKLICPGM) to list installed licensed programs. Look for 'Administration Runtime Expert' or similar IBM i administration products.
    Affected if The product is present on the system
  2. Determine the installed version of Administration Runtime Expert
    Use the 'Display Software Version' command (DSPSFWRSC) or check the program details in WRKLICPGM for the Administration Runtime Expert component. Note the version number (7.2, 7.3, 7.4, or 7.5).
    Affected if The version is 7.2, 7.3, 7.4, or 7.5 (any version in the 7.2-7.5 range)
  3. Confirm the Administration Runtime Expert service is accessible
    Check if the Administration Runtime Expert functions are available to users. This may be accessible through the IBM i menu system (GO CMDADM) or via web interfaces if the product includes a web component.
    Affected if The service or interface is accessible to local users on the system
  4. Review user authorities to Administration Runtime Expert components
    Use 'Display User Authority' (DSPUSRAUT) or 'Edit Object Authority' (EDTOBJAUT) on the Administration Runtime Expert libraries or objects to see which users have access. Look for users who may have elevated privileges or access beyond their intended authorization level.
    Affected if Users have been granted access they should not have, or if untrusted local users have any access to the product

The environment is affected if IBM Administration Runtime Expert for i versions 7.2 through 7.5 is installed and accessible, allowing local authenticated users to potentially view sensitive information beyond their authorized permissions.

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 security patch for CVE-2023-42006 when available. Until then, limit local access to the IBM i system to trusted users only and follow least-privilege principles for user authorities.

Fix this in I Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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