ViosApplication · Ibm

CVE-2024-47115

HIGH · 7.8 CVSS v3.1 Published 2024-12-07
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 AIX 7.2, 7.3 and VIOS 3.1 and 4.1 could allow a local user to execute arbitrary commands on the system due to improper neutralization of input.

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

Local command injection vulnerability in IBM AIX 7.2, 7.3 and VIOS 3.1, 4.1 allows an authenticated local user to execute arbitrary commands due to improper neutralization of input. This likely stems from insufficient sanitization of user-supplied parameters in a system utility or service.

MitigationApply IBM security patches for AIX and VIOS as released for this vulnerability. Identify and patch all affected AIX and VIOS systems following IBM's remediation guidance.

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
ViosApplication
Affected:= 3.1= 4.1
AixOperating system
Affected:= 7.2= 7.3

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 AIX operating system version
    Run 'oslevel -s' or 'lsattr -E -l sys0 | grep oslevel' to retrieve the installed AIX version
    Affected if The version output shows 7.2.x or 7.3.x (any TL/SP level within these major versions)
  2. Check VIOS (Virtual I/O Server) version
    Run 'ioslevel' or 'oem_platform_level' on the VIOS system to get the version number
    Affected if The version output shows 3.1.x or 4.1.x (any fix level within these major versions)
  3. Verify exact product installation
    Run 'lslpp -l | grep -i bos' to list installed AIX file sets and confirm AIX is the base operating system
    Affected if Output shows AIX 7.2 or AIX 7.3 file sets installed (such as bos.base)

Your system is affected if it runs IBM AIX 7.2 or 7.3, or VIOS 3.1 or 4.1, and an authenticated local user could potentially exploit the command injection via the vulnerable utility/service.

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 security patches for AIX and VIOS as released for this vulnerability. Identify and patch all affected AIX and VIOS systems following IBM's remediation guidance.

Fix this in Vios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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