Поиск уязвимостей
Количество 46
Количество 46
CVE-2022-23305
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
CVE-2022-23305
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as ...
GHSA-f7vh-qwp3-x37m
Deserialization of Untrusted Data in Apache Log4j
GHSA-65fg-84f6-3jq3
SQL Injection in Log4j 1.2.x
BDU:2023-07205
Уязвимость адаптера JDBCAppender программы для журналирования Java-программ Log4j, позволяющая нарушителю выполнять произвольные SQL-запросы к базе данных
BDU:2022-01069
Уязвимость библиотеки журналирования Java-программ Log4j, связанная с восстановлением в памяти недостоверных данных, позволяющая нарушителю выполнить произвольный код
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2022-23305 By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. | CVSS3: 9.8 | 67% Средний | почти 5 лет назад |
| CVE-2022-23305 By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as ... | CVSS3: 9.8 | 67% Средний | почти 5 лет назад |
| GHSA-f7vh-qwp3-x37m Deserialization of Untrusted Data in Apache Log4j | CVSS3: 9.8 | 54% Средний | почти 5 лет назад |
| GHSA-65fg-84f6-3jq3 SQL Injection in Log4j 1.2.x | CVSS3: 9.8 | 67% Средний | почти 5 лет назад |
 | BDU:2023-07205 Уязвимость адаптера JDBCAppender программы для журналирования Java-программ Log4j, позволяющая нарушителю выполнять произвольные SQL-запросы к базе данных | CVSS3: 9.8 | 67% Средний | почти 5 лет назад |
| BDU:2022-01069 Уязвимость библиотеки журналирования Java-программ Log4j, связанная с восстановлением в памяти недостоверных данных, позволяющая нарушителю выполнить произвольный код | CVSS3: 9.8 | 54% Средний | почти 5 лет назад |
Уязвимостей на страницу