Technical impact
This vulnerability arises in log4net’s FileAppender, RollingFileAppender, UdpAppender and SmtpAppender when a character encoding that uses best‑fit fallback is applied after the XML layout has escaped user data. Fullwidth characters such as U+FF1C, U+FF1E and U+FF02 are silently converted into <, > and ", allowing an attacker to inject crafted XML fragments that become part of the log file. The result is forged log events, for example fake audit entries, which can mislead analysis and compromise log integrity. The weakness is an instance of Improper Output Neutralization for Logs (CWE‑117). No arbitrary code execution or direct access is gained; the flaw affects only the log content.
Affected Systems
Apache Software Foundation’s log4net library, versions beginning with 1.2.9 and continuing through all releases prior to 3.6.0, is vulnerable. On the .NET Framework, the default ANSI single‑byte code page renders the flaw without additional configuration, while on .NET Core / .NET 5+ a single‑byte encoding such as ISO‑8859‑1 must be configured for the issue to manifest.
Risk and Exploitability
The CVSS score of 5.3 classifies the flaw as moderate; the EPSS score is not available, and the vulnerability is not listed in CISA KEV. Exploitation requires the attacker to supply input that is logged, which can arise in a variety of contexts such as web applications, services, or any component that writes to a log4net FileAppender or related appenders. The attack scale is limited to the integrity of log data; however, forged logs can be used to mislead investigations or cover malicious activity. The best‑fit conversion is performed automatically by the encoding system, so no special steps are needed beyond having the vulnerable configuration.