Vulnerabilities on Apache Log4j
Show older comments
Running 2024b version, i have been notified that:
\java\jarext\aps_impl\pubsub_impl_java\pubsub_impl.jar
\java\jarext\lais_server_impl\lais_server_impl.jar
\java\jarext\log4j-core-2.17.1.jar
belongs to a version of Apache Log4j on the remote host that is 2.0-alpha1 through 2.25.3. It is, therefore, affected by a vulnerability:
- The XmlLayout fails to sanitize characters forbidden by the XML 1.0 specification, producing invalid XML output whenever a log message or MDC value contains such characters. Depending on the StAX implementation, this causes either malformed XML or exceptions during logging. (CVE-2026-34480)
Can you confirm that? Should i expect a patch?
Thanks,
Giuseppe
1 Comment
Torsten
about 22 hours ago
If you want an official answer, contact support:
You might want to check this answer first:
Answer from AI:
The flagged .jar files in MATLAB R2024b do contain Log4j 2.17.1, which is listed as vulnerable to CVE-2026-34480, but MATLAB itself is not actually exploitable and you should not expect a standalone patch for R2024b. [1, 2, 3]
Here is what is happening and what you should know for your security or compliance team:
1. Confirmation of the Findings
- Valid library detection. Your vulnerability scanner (such as Tenable or Nessus) is accurately reading the version metadata inside log4j-core-2.17.1.jar and the shaded/bundled components inside pubsub_impl.jar and lais_server_impl.jar. [1, 2]
- Vulnerability details. According to the National Vulnerability Database (NVD), CVE-2026-34480 (CVSS 6.9 Medium) affects Apache Log4j Core versions 2.0-alpha1 through 2.25.3. When XmlLayout is used, forbidden XML 1.0 characters in log messages or MDC values are not sanitized, which can cause malformed XML or dropped log records. [1, 2, 3]
2. Is MATLAB R2024b Actually Affected?
- Not exploitable in default MATLAB configurations. According to MathWorks Security Assessments on MATLAB Answers, MATLAB bundles these Log4j packages internally, but it does not configure or invoke XmlLayout in its logging setup. Because the vulnerable layout class is never called, the vulnerability cannot be triggered during normal MATLAB operation. [1, 2]
- False-positive scanner behavior. Automated file-system scanners only check the .jar version number (2.17.1 < 2.25.4) rather than checking whether XmlLayout is active. [1]
3. Should You Expect a Patch?
- No standalone patch for R2024b. MathWorks has stated that customers do not need to take action regarding this CVE because the vulnerable feature is unused. Additionally, MathWorks rarely backports third-party .jar dependency bumps to older releases like R2024b unless there is an active, exploitable security impact.
- Do not manually replace the .jar files. Manually swapping log4j-core-2.17.1.jar with 2.25.4 inside the \java\jarext\ directory is unsupported by MathWorks and can break internal Java dependencies or license/server communication tools.
- Next steps for compliance. If you are answering to an internal security audit or an air-gapped scanner finding, you can document this as a false positive / non-exploitable finding using MathWorks' official stance on MATLAB Answers or open a ticket via MathWorks Support to request a formal vendor attestation letter for your Plan of Action and Milestones (POA&M). [1, 2, 3]
Accepted Answer
More Answers (0)
Categories
Find more on MATLAB Support Package for Arduino Hardware in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!