Apache log4net: AdoNetAppender loses an event whose text the database cannot store
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Apache Software Foundation | Apache log4net | unaffected |
|
||||||
| Apache Software Foundation | Apache log4net | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Apache | Log4net |
|
||||||||
| Apache | Log4net |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Apache
Apache log4net |
|
| Vendors & Products |
Apache
Apache log4net |
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Improper Neutralization of Null Byte or NUL Character vulnerability in the AdoNetAppender of Apache log4net. Text parameters were bound unchanged, so a NUL character or an unpaired UTF-16 surrogate reached the database as it was. A database that refuses such a value, such as PostgreSQL, rejected the insert and the event was lost; only the first such loss per appender was reported. A party whose data reaches a log message could suppress that event. This issue affects Apache log4net: from 1.2.9 before 3.6.0. Users are recommended to upgrade to version 3.6.0, which fixes the issue. | |
| Title | Apache log4net: AdoNetAppender loses an event whose text the database cannot store | |
| Weaknesses | CWE-158 | |
| References |
| |
| Metrics |
cvssV3_1
|
No data.