Qos

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any Qos product.

RSS Feeds for Qos security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in Qos products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by Qos Sorted by Most Security Vulnerabilities since 2018

Qos Logback5 vulnerabilities

Qos Reload4j5 vulnerabilities

Qos Slf4j1 vulnerability

By the Year

In 2026 there have been 0 vulnerabilities in Qos. Qos did not have any published security vulnerabilities last year.

Year	Vulnerabilities	Average Score
2026	0	0.00
2025	0	0.00
2024	1	0.00
2023	2	7.50
2022	3	9.13
2021	2	6.60
2020	1	0.00
2019	0	0.00
2018	1	0.00

It may take a day or so for new Qos vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Qos Security Vulnerabilities

CVE	Date	Vulnerability	Products
CVE-2024-12801	Dec 19, 2024	SSRF via SaxEventRecorder in QOS.CH logback 0.1-1.3.14 & 1.4.0-1.5.12 Server-Side Request Forgery (SSRF) in SaxEventRecorder by QOS.CH logback version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 on the Java platform, allows an attacker to forge requests by compromising logback configuration files in XML. The attacks involves the modification of DOCTYPE declaration in XML configuration files.	Logback
CVE-2023-6481	Dec 04, 2023	Logback Receiver DoS via Serialization Before 1.4.13 A serialization vulnerability in logback receiver component part of logback version 1.4.13, 1.3.13 and 1.2.12 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.	Logback
CVE-2023-6378	Nov 29, 2023	logback 1.4.11 Receiver SerDoS Vulnerability A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.	Logback
CVE-2022-23307	Jan 18, 2022	CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.	Reload4j
CVE-2022-23305	Jan 18, 2022	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 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.	Reload4j
CVE-2022-23302	Jan 18, 2022	JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. 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.	Reload4j
CVE-2021-42550	Dec 16, 2021	In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.	Logback
CVE-2020-9493	Jun 16, 2021	A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.	Reload4j
CVE-2020-9488	Apr 27, 2020	Improper validation of certificate with host mismatch in Apache Log4j SMTP appender 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	Reload4j
CVE-2018-8088	Mar 20, 2018	org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to bypass intended access restrictions via crafted data. EventData in the slf4j-ext module in QOS.CH SLF4J, has been fixed in SLF4J versions 1.7.26 later and in the 2.0.x series.	Slf4j