log4net is vulnerable to Improper Handling of Unicode Encoding
53
CVE Score
Medium
Improper Handling of Unicode Encoding
Before the fix, SmtpPickupDirAppender wrote its pickup-directory mail with File.CreateText, whose UTF-8 encoder throws on characters it cannot encode, such as an unpaired UTF-16 surrogate in a logged message. One such event, supplied by any party whose data reaches a log message, aborted the whole batch write: the remaining buffered events were never written and a truncated mail was left for the pickup service to send. Only applications that configure SmtpPickupDirAppender are exposed. The fix writes with a non-throwing UTF-8 encoder and escapes unpaired surrogates, so one unencodable event no longer discards the batch.
Upgrade the log4net package to 3.5.0 or later.
You are affected if you are using a version that falls within the vulnerable range and use a SmtpPickupDirAppender whose logged messages include content from other parties, such as user-supplied request data.
1.2.10 - 3.4.0
Fixed in 3.5.0log4net is vulnerable to Improper Handling of Unicode Encoding in versions 1.2.10 - 3.4.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.