qos vulnerabilities
Recent CVEs affecting qos products. 9 tracked.
qos has 9 tracked vulnerabilities, 4 critical. A fixed release or vendor patch exists for 8. Most recent: 2023-12-04. Highest priority: CVE-2022-23305 (score 77/100).
- CVE-2020-9493 CRITICAL 9.8 UPGRADE UPGRADE A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code
- CVE-2023-6481 HIGH 7.1 DOWNGRADE A serialization vulnerability in logback receiver component part of logback version 1.4.13, 1.3.13 and 1.2.12
- CVE-2023-6378 HIGH 7.1 UPGRADE A serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker
- CVE-2022-23307 HIGH 8.8 UPGRADE UPGRADE CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw
- CVE-2022-23305 CRITICAL 9.8 UPGRADE MITIGATE By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the val
- CVE-2022-23302 HIGH 8.8 UPGRADE MITIGATE JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has
- CVE-2021-42550 MEDIUM 6.6 UPGRADE DOWNGRADE In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations f
- CVE-2018-8088 CRITICAL 9.8 UPGRADE DOWNGRADE org.slf4j.ext.EventData in the slf4j-ext module in QOS.CH SLF4J before 1.8.0-beta2 allows remote attackers to
- CVE-2017-5929 CRITICAL 9.8 UPGRADE DOWNGRADE QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketRecei
FAQ
How do I fix qos vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is qos being exploited right now?
None of the tracked qos CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which qos CVE should I patch first?
CVE-2022-23305 currently ranks highest (77/100): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the val.