Skip to content

Remote code injection, Improper Input Validation and Uncontrolled Recursion in Log4j library

Critical severity GitHub Reviewed Published Dec 21, 2021 in PowerNukkit/PowerNukkit • Updated Jan 11, 2023

Package

maven org.powernukkit:powernukkit (Maven)

Affected versions

<= 1.5.2.0

Patched versions

1.5.2.1

Description

Summary

The version used of Log4j, the library used for logging by PowerNukkit, is subject to a remote code execution vulnerability via the ldap JNDI parser.
It's well detailed at CVE-2021-44228 and CVE-2021-45105(GHSA-p6xc-xr62-6r2g).

Impact

Malicious client code could be used to send messages and cause remote code execution on the server.

Patches

PowerNukkit 1.5.2.1 is a patch-release that only updates the Log4j version to 2.17.0 and should be used instead of 1.5.2.0.
All versions prior to 1.5.2.1 are affected and are not patched.

Workarounds

If you can't upgrade, you can use the -Dlog4j2.formatMsgNoLookups=true startup argument as remediation, as this prevents the vulnerability from happening.

References

GHSA-jfh8-c2jp-5v3q
GHSA-p6xc-xr62-6r2g

For more information

If you have any questions or comments about this advisory:

References

@joserobjr joserobjr published to PowerNukkit/PowerNukkit Dec 21, 2021
Reviewed Jan 4, 2022
Published to the GitHub Advisory Database Jan 6, 2022
Last updated Jan 11, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-3qpm-h9ch-px3c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.