<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T12:34:22.068011+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/alsa-2022:0290</id>
    <title>ALSA-2022:0290 — Important: parfait:0.5 security update</title>
    <updated>2026-10-03T12:34:22.949176+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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.</p>
<p>Security Fix(es):</p>
<p>* log4j: SQL injection in Log4j 1.x when application is configured to use JDBCAppender (CVE-2022-23305)</p>
<p>* log4j: Unsafe deserialization flaw in Chainsaw log viewer (CVE-2022-23307)</p>
<p>* log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender (CVE-2021-4104)</p>
<p>* log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink (CVE-2022-23302)</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/alsa-2022:0290"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2022-00031</id>
    <title>bdu:2022-00031</title>
    <updated>2026-10-03T12:34:22.949357+00:00</updated>
    <content>bdu:2022-00031</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2022-00031"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2021-ale-022</id>
    <title>certfr-2021-ale-022 — Une vulnérabilité a été découverte dans la bibliothèque de
journalisation Apache log4j. Cette bibliothèque est très sou…</title>
    <updated>2026-10-03T12:34:22.949390+00:00</updated>
    <content>certfr-2021-ale-022</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2021-ale-022"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2021-avi-951</id>
    <title>certfr-2021-avi-951 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de
RedHat. Certaines d'entre elles permettent à un…</title>
    <updated>2026-10-03T12:34:22.949462+00:00</updated>
    <content>certfr-2021-avi-951</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2021-avi-951"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2022-01775</id>
    <title>cnvd-2022-01775</title>
    <updated>2026-10-03T12:34:22.949490+00:00</updated>
    <content>cnvd-2022-01775</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2022-01775"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-322648</id>
    <title>EUVD-2026-322648</title>
    <updated>2026-10-03T12:34:22.949512+00:00</updated>
    <content>EUVD-2026-322648</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-322648"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-4104</id>
    <title>fkie_cve-2021-4104</title>
    <updated>2026-10-03T12:34:22.949531+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-4104"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fp5r-v3w9-4333</id>
    <title>GHSA-fp5r-v3w9-4333 — JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data</title>
    <updated>2026-10-03T12:34:22.949572+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: log4j:log4j, Maven: org.zenframework.z8.dependencies.commons:log4j-1.2.17</p>
<p>JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fp5r-v3w9-4333"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-4104</id>
    <title>gsd-2021-4104</title>
    <updated>2026-10-03T12:34:22.949615+00:00</updated>
    <content>gsd-2021-4104</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-4104"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2022-1513</id>
    <title>OESA-2022-1513 — log4j12 security update</title>
    <updated>2026-10-03T12:34:22.949635+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP1: log4j12, openEuler:20.03-LTS-SP2: log4j12, openEuler:20.03-LTS-SP3: log4j12</p>
<p>With log4j it is possible to enable logging at runtime without modifying the application binary.

Security Fix(es):

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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.(CVE-2021-4104)

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.(CVE-2022-23307)

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. Apac…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2022-1513"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2021:1612-1</id>
    <title>openSUSE-SU-2021:1612-1 — Security update for log4j12</title>
    <updated>2026-10-03T12:34:22.949742+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for log4j12</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2021:1612-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2021:5107</id>
    <title>RHSA-2021:5107 — Red Hat Security Advisory: OpenShift Container Platform 4.7.40 security update</title>
    <updated>2026-10-03T12:34:22.949781+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender log4j-core: Remote code execution in Log4j 2.x when logs contain an attacker-controlled string value log4j-core: DoS in log4j 2.x with thread context message pattern and context lookup pattern (incomplete fix for CVE-2021-44228)</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2021:5107"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/sesb-2021-347-01</id>
    <title>SESB-2021-347-01 — Apache Log4j Vulnerabilities (Log4Shell)</title>
    <updated>2026-10-03T12:34:22.949826+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Schneider Electric is aware of the vulnerabilities impacting Apache Log4j, including CVE-2021-44228, also known as Log4Shell. Our cybersecurity team is actively investigating the impact of the vulnerability on Schneider Electric offers and will continuously update this notification as information becomes available.
In the meantime, customers should immediately ensure they have implemented cybersecurity best practices across their operations to protect themselves from exploitation of this vulnerability. Where appropriate, this includes locating their systems and remotely accessible devices behind firewalls; installing physical controls to prevent unauthorized access; preventing mission-critical systems and devices from being accessed from outside networks; and following the recommended mitigations and general security recommendations below.
Please subscribe to the Schneider Electric security notification service to be informed of critical updates to this notification, including information on affected products and remediation plans:
https://www.se.com/ww/en/work/support/cybersecurity/security-notifications.jsp
For additional information and support, please contact your Schneider Electric sales or service representative or Schneider Electric’s Customer Care Center.
August 2022 Update: Remediation update for Eurotherm Data Reviewer.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/sesb-2021-347-01"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2021:14866-1</id>
    <title>SUSE-SU-2021:14866-1 — Security update for log4j</title>
    <updated>2026-10-03T12:34:22.949879+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for log4j</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2021:14866-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-4104</id>
    <title>UBUNTU-CVE-2021-4104</title>
    <updated>2026-10-03T12:34:22.949909+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-4104"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0520</id>
    <title>WID-SEC-W-2022-0520 — Apache log4j: Schwachstelle ermöglicht Ausführen von beliebigem Programmcode</title>
    <updated>2026-10-03T12:34:22.949953+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um beliebigen Programmcode mit den Rechten des Dienstes auszuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2022-0520"/>
  </entry>
</feed>
