https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T12:11:48.902715+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/alsa-2022:0290 ALSA-2022:0290 — Important: parfait:0.5 security update 2026-10-03T12:11:49.204624+00:00

Affected: AlmaLinux:8: parfait, AlmaLinux:8: parfait-examples, AlmaLinux:8: parfait-javadoc, AlmaLinux:8: pcp-parfait-agent, AlmaLinux:8: si-units, AlmaLinux:8: si-units-javadoc, AlmaLinux:8: unit-api, AlmaLinux:8: unit-api-javadoc, AlmaLinux:8: uom-lib, AlmaLinux:8: uom-lib-javadoc and 5 more

Parfait is a Java performance monitoring library that collects metrics and exposes them through a variety of outputs. It provides APIs for extracting performance metrics from the JVM and other sources. It interfaces to Performance Co-Pilot (PCP) using the Memory Mapped Value (MMV) machinery for extremely lightweight instrumentation.

Security Fix(es):

* log4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender (CVE-2022-23305)

* log4j: Unsafe deserialization flaw in Chainsaw log viewer (CVE-2022-23307)

* log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender (CVE-2021-4104)

* log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink (CVE-2022-23302)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

 https://cve.radiocsirt.org/vuln/bdu:2023-07205 bdu:2023-07205 2026-10-03T12:11:49.204743+00:00 bdu:2023-07205 https://cve.radiocsirt.org/vuln/certfr-2022-avi-369 certfr-2022-avi-369 — De multiples vulnérabilités ont été découvertes dans Oracle WebLogic Server. Certaines d'entre elles permettent à un at… 2026-10-03T12:11:49.204761+00:00 certfr-2022-avi-369 https://cve.radiocsirt.org/vuln/cnvd-2022-08370 cnvd-2022-08370 2026-10-03T12:11:49.204778+00:00 cnvd-2022-08370 https://cve.radiocsirt.org/vuln/euvd-2026-321941 EUVD-2026-321941 2026-10-03T12:11:49.204790+00:00 EUVD-2026-321941 https://cve.radiocsirt.org/vuln/fkie_cve-2022-23305 fkie_cve-2022-23305 2026-10-03T12:11:49.204800+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.

 https://cve.radiocsirt.org/vuln/ghsa-65fg-84f6-3jq3 GHSA-65fg-84f6-3jq3 — SQL Injection in Log4j 1.2.x 2026-10-03T12:11:49.204824+00:00

Affected: Maven: log4j:log4j, Maven: org.zenframework.z8.dependencies.commons:log4j-1.2.17

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.

 https://cve.radiocsirt.org/vuln/gsd-2022-23305 gsd-2022-23305 2026-10-03T12:11:49.204851+00:00 gsd-2022-23305 https://cve.radiocsirt.org/vuln/oesa-2022-1781 OESA-2022-1781 — log4j12 security update 2026-10-03T12:11:49.204862+00:00

Affected: openEuler:20.03-LTS-SP1: log4j12, openEuler:20.03-LTS-SP3: log4j12

With log4j it is possible to enable logging at runtime without modifying the application binary. Security Fix(es): 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)

 https://cve.radiocsirt.org/vuln/opensuse-su-2022:0038-1 openSUSE-SU-2022:0038-1 — Security update for kafka 2026-10-03T12:11:49.204887+00:00

Security update for kafka

 https://cve.radiocsirt.org/vuln/rhsa-2022:0289 RHSA-2022:0289 — Red Hat Security Advisory: parfait:0.5 security update 2026-10-03T12:11:49.204906+00:00

log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink log4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender log4j: Unsafe deserialization flaw in Chainsaw log viewer

 https://cve.radiocsirt.org/vuln/suse-su-2022:0212-1 SUSE-SU-2022:0212-1 — Security update for log4j 2026-10-03T12:11:49.204927+00:00

Security update for log4j

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-23305 UBUNTU-CVE-2022-23305 2026-10-03T12:11:49.204943+00:00

Affected: Ubuntu:Pro:14.04:LTS: apache-log4j1.2, Ubuntu:Pro:16.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j1.2, Ubuntu:20.04:LTS: apache-log4j1.2

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.

 https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0169 WID-SEC-W-2022-0169 — Oracle MySQL: Mehrere Schwachstellen 2026-10-03T12:11:49.204969+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Oracle MySQL ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.