Qos vulnerabilitiesNone on the known-exploited list.
Qos has 10 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Reload4j, with 5. If you run Qos software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Qos vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Qos's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Qos flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 67%CVE-2022-23305Critical
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.
- 64%CVE-2022-23302High
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...
- 54%CVE-2022-23307High
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw.
- 15%CVE-2018-8088Critical
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.
- 8.2%
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender.
- 7.5%CVE-2017-5929Critical
QOS.ch Logback before 1.2.0 has a serialization vulnerability affecting the SocketServer and ServerSocketReceiver components.
- 4.8%CVE-2021-42550Medium
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.
- 4.6%CVE-2020-9493Critical
A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.
- 0.9%CVE-2023-6378High
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.
- 0.7%CVE-2023-6481High
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.
All Qos products we track.
3 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Qos? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Qos on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 10 published vulnerabilities across 3 products and 174 versions from Qos.
None of Qos's vulnerabilities is on the list of flaws known to be exploited today.
Reload4j, with 5 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Qos products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.