What is the severity of CVE-2019-4381?

The severity of CVE-2019-4381 is classified as high due to the potential for sensitive information exposure.

How do I fix CVE-2019-4381?

To fix CVE-2019-4381, update your IBM i operating system to the latest version that addresses this vulnerability.

Who is affected by CVE-2019-4381?

CVE-2019-4381 affects IBM i versions 7.2 and 7.3.

What kind of information can be obtained through CVE-2019-4381?

CVE-2019-4381 allows local attackers to obtain sensitive HMC credentials.

What attack vector is utilized in CVE-2019-4381?

CVE-2019-4381 is exploited using the REST API for advanced node failure detection in IBM i clustering.

Vulnerability/
CVE-2019-4381

medium

5.9

CWE

255

14/6/2019

16/9/2024

CVE-2019-4381

First published: Fri Jun 14 2019(Updated: )

IBM i 7.27.3 Clustering could allow a local attacker to obtain sensitive information, caused by the use of advanced node failure detection using the REST API to interface with the HMC. An attacker could exploit this vulnerability to obtain HMC credentials. IBM X-Force ID: 162159.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM OS/400	=7.2
IBM OS/400	=7.3

Remedy

https://www.ibm.com/support/docview.wss?uid=ibm10887369

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-4381?
The severity of CVE-2019-4381 is classified as high due to the potential for sensitive information exposure.
How do I fix CVE-2019-4381?
To fix CVE-2019-4381, update your IBM i operating system to the latest version that addresses this vulnerability.
Who is affected by CVE-2019-4381?
CVE-2019-4381 affects IBM i versions 7.2 and 7.3.
What kind of information can be obtained through CVE-2019-4381?
CVE-2019-4381 allows local attackers to obtain sensitive HMC credentials.
What attack vector is utilized in CVE-2019-4381?
CVE-2019-4381 is exploited using the REST API for advanced node failure detection in IBM i clustering.

agent/type
agent/softwarecombine
agent/references
agent/weakness
agent/severity
agent/remedy
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/ibm
canonical/ibm os/400
version/ibm os/400/7.2
version/ibm os/400/7.3

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2019-4381?
The severity of CVE-2019-4381 is classified as high due to the potential for sensitive information exposure.
How do I fix CVE-2019-4381?
To fix CVE-2019-4381, update your IBM i operating system to the latest version that addresses this vulnerability.
Who is affected by CVE-2019-4381?
CVE-2019-4381 affects IBM i versions 7.2 and 7.3.
What kind of information can be obtained through CVE-2019-4381?
CVE-2019-4381 allows local attackers to obtain sensitive HMC credentials.
What attack vector is utilized in CVE-2019-4381?
CVE-2019-4381 is exploited using the REST API for advanced node failure detection in IBM i clustering.