🛡️ MGASA-2022-0002 — log4j
Description
Updated log4j packages fix security vulnerability
Apache Log4j2 is vulnerable to a remote code execution (RCE) attack where
an attacker with permission to modify the logging configuration file can
construct a malicious configuration using a JDBC Appender with a data
source referencing a JNDI URI which can execute remote code. This issue is
fixed by limiting JNDI data source names to the java protocol
Affected software
MGASA-2022-0002 is recorded against 1 package.
- log4j (fixed in 2.17.1-1.mga8)
Timeline and source
Published on 3 January 2022 and last revised on 16 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
advisories.mageia.org (Advisory)
bugs.mageia.org (Report)
www.openwall.com (Web)
lists.opensuse.org (Web)
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| log4j | — | 2.17.1-1.mga8 |
References
Similar Threats
- Unknown CLSA-2026-1779124827
- Medium CVE-2026-34477
- High CVE-2026-34478
- High CVE-2026-34479
- High CVE-2026-34480
More MGASA 2022 advisories
Browse all of MGASA 2022 in the advisory index.
Free Vulnerability Check
Is your site affected by MGASA-2022-0002?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against MGASA-2022-0002 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.