NVIDIA, HPE Products Affected by Log4j Vulnerabilities

NVIDIA and Hewlett Packard Enterprise (HPE) have confirmed that some of their products are affected by the recently disclosed vulnerabilities in the Apache Log4j logging utility.

A total of three vulnerabilities were identified in the utility – namely CVE-2021-44228 (aka Log4Shell), CVE-2021-45046 and CVE‑2021‑45105 – and at least two of them have been exploited in malicious attacks.

Shortly after the issues became public, NVIDIA and HPE started investigating which of their products are affected, and both of them already released patches and mitigations to resolve the bugs or prevent potential exploitation attempts.

[ READ: Log4Shell Tools and Resources for Defenders – Continuously Updated ]

In an advisory updated on Wednesday, NVIDIA confirmed that the Log4j security defects affect CUDA Toolkit Visual Profiler and Nsight Eclipse Edition, NetQ, and vGPU Software License Server.

The company also notes that, while the DGX Systems do not include the Log4j Java library, users might have installed the vulnerable utility as additional software. Thus, NVIDIA decided to release fixes for multiple DGX OS releases as well.

NVIDIA’s GeForce Experience and GeForceNOW client software, GPU Display Drivers for Windows and Linux, L4T Jetson products, SHIELD TV, and networking products (except for NetQ) are not affected.

HPE, on the other hand, says that some of its products are also affected by CVE-2021-4104, a deserialization of untrusted data vulnerability that can be triggered by an attacker with access to the Log4j configuration and which results in remote code execution (only Log4j 1.2 configured to use JMSAppender is affected).

The company has identified roughly 60 products that use the vulnerable library and has already published security notices (including patches and mitigations) and security bulletins for them.

NVIDIA and HPE are only two of the many companies that are likely affected by the Log4j vulnerabilities. Earlier this week, Google said it identified 36,000 Java packages in the Maven Central repository that still use vulnerable Log4j versions.

Related: Five Eyes Nations Issue Joint Guidance on Log4j Vulnerabilities

Related: Chinese Government Punishes Alibaba for Not Telling It First About Log4Shell Flaw

Related: SAP Patches Log4Shell Vulnerability in 20 Applications

view counter

Ionut Arghire is an international correspondent for SecurityWeek.

Previous Columns by Ionut Arghire:

Don't forget to share

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *