QOS reload4j 1.2.18.1

CPE Details

QOS reload4j 1.2.18.1
1.2.18.1
2022-04-08
08h18 +00:00
2022-04-08
16h23 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:qos:reload4j:1.2.18.1:*:*:*:*:*:*:*

Informations

Vendor

qos

Product

reload4j

Version

1.2.18.1

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2022-23305 2022-01-18 14h25 +00:00 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.
9.8
Critical
CVE-2020-9488 2020-04-27 13h36 +00:00 Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1
3.7
Low