Debian DLA-2905-1 : apache-log4j1.2 - LTS security update - Nessus

High   Plugin ID: 157261

This page contains detailed information about the Debian DLA-2905-1 : apache-log4j1.2 - LTS security update Nessus plugin including available exploits and PoCs found on GitHub, in Metasploit or Exploit-DB for verifying of this vulnerability.

Plugin Overview


ID: 157261
Name: Debian DLA-2905-1 : apache-log4j1.2 - LTS security update
Filename: debian_DLA-2905.nasl
Vulnerability Published: 2021-12-14
This Plugin Published: 2022-01-31
Last Modification Time: 2022-04-26
Plugin Version: 1.3
Plugin Type: local
Plugin Family: Debian Local Security Checks
Dependencies: ssh_get_info.nasl
Required KB Items [?]: Host/Debian/dpkg-l, Host/Debian/release, Host/local_checks_enabled

Vulnerability Information


Severity: High
Vulnerability Published: 2021-12-14
Patch Published: 2022-01-31
CVE [?]: CVE-2021-4104, CVE-2022-23302, CVE-2022-23305, CVE-2022-23307
CPE [?]: cpe:/o:debian:debian_linux:9.0, p-cpe:/a:debian:debian_linux:liblog4j1.2-java, p-cpe:/a:debian:debian_linux:liblog4j1.2-java-doc

Synopsis

The remote Debian host is missing one or more security-related updates.

Description

The remote Debian 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-2905 advisory.

- 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)

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

- 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)

- 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)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Solution

Upgrade the apache-log4j1.2 packages.

For Debian 9 stretch, these problems have been fixed in version 1.2.17-7+deb9u2.

Public Exploits


Target Network Port(s): N/A
Target Asset(s): N/A
Exploit Available: True (GitHub)
Exploit Ease: Exploits (PoCs) are available

Here's the list of publicly known exploits and PoCs for verifying the Debian DLA-2905-1 : apache-log4j1.2 - LTS security update vulnerability:

  1. GitHub: https://github.com/Diablo5G/Certification-Prep
    [CVE-2021-4104]
  2. GitHub: https://github.com/GGongnanE/TodayILearned
    [CVE-2021-4104]
  3. GitHub: https://github.com/HackJava/Log4j2
    [CVE-2021-4104]
  4. GitHub: https://github.com/HynekPetrak/log4shell-finder
    [CVE-2021-4104]
  5. GitHub: https://github.com/NiftyBank/java-app
    [CVE-2021-4104]
  6. GitHub: https://github.com/PAXSTORE/paxstore-openapi-java-sdk
    [CVE-2021-4104]
  7. GitHub: https://github.com/Qualys/log4jscanwin
    [CVE-2021-4104]
  8. GitHub: https://github.com/TheInterception/Log4JPentester
    [CVE-2021-4104: Automated pentesting tools and vulnerability fixes for Log4Shell CVE-2021-44228 / ...]
  9. GitHub: https://github.com/TheInterception/Log4J-Simulation-Tool
    [CVE-2021-4104: Vulerability analysis, patch management and exploitation tool CVE-2021-44228 / ...]
  10. GitHub: https://github.com/apache/logging-log4j1
    [CVE-2021-4104]
  11. GitHub: https://github.com/cckuailong/log4shell_1.x
    [CVE-2021-4104: Log4j 1.x RCE Poc -- CVE-2021-4104]
  12. GitHub: https://github.com/davejwilson/azure-spark-pools-log4j
    [CVE-2021-4104]
  13. GitHub: https://github.com/logpresso/CVE-2021-44228-Scanner
    [CVE-2021-4104]
  14. GitHub: https://github.com/ltslog/ltslog
    [CVE-2021-4104]
  15. GitHub: https://github.com/open-AIMS/log4j
    [CVE-2021-4104: Log4j version 1.2.17 without the offending class responsible for CVE-2021-4104.]
  16. GitHub: https://github.com/srhercules/log4j_mass_scanner
    [CVE-2021-4104]
  17. GitHub: https://github.com/syslog-ng/syslog-ng
    [CVE-2021-4104]
  18. GitHub: https://github.com/thl-cmk/CVE-log4j-check_mk-plugin
    [CVE-2021-4104]
  19. GitHub: https://github.com/whitesource-ps/ws-bulk-report-generator
    [CVE-2021-4104]
  20. GitHub: https://github.com/whitesource/log4j-detect-distribution
    [CVE-2021-4104]
  21. GitHub: https://github.com/AlphabugX/CVE-2022-23302
    [CVE-2022-23302: ![image](https://user-images.githubusercontent.com/27001865/150348452-38595c7d-8f16-4 ...]
  22. GitHub: https://github.com/HynekPetrak/log4shell-finder
    [CVE-2022-23302]
  23. GitHub: https://github.com/apache/logging-log4j1
    [CVE-2022-23302]
  24. GitHub: https://github.com/davejwilson/azure-spark-pools-log4j
    [CVE-2022-23302]
  25. GitHub: https://github.com/logpresso/CVE-2021-44228-Scanner
    [CVE-2022-23302]
  26. GitHub: https://github.com/ltslog/ltslog
    [CVE-2022-23302]
  27. GitHub: https://github.com/thl-cmk/CVE-log4j-check_mk-plugin
    [CVE-2022-23302]
  28. GitHub: https://github.com/whitesource/log4j-detect-distribution
    [CVE-2022-23302]
  29. GitHub: https://github.com/AlphabugX/CVE-2022-RCE
    [CVE-2022-23305: Test 反向辣鸡数据投放 CVE-2022-23305 工具 利用 教程 Exploit POC]
  30. GitHub: https://github.com/apache/logging-log4j1
    [CVE-2022-23305]
  31. GitHub: https://github.com/davejwilson/azure-spark-pools-log4j
    [CVE-2022-23305]
  32. GitHub: https://github.com/logpresso/CVE-2021-44228-Scanner
    [CVE-2022-23305]
  33. GitHub: https://github.com/ltslog/ltslog
    [CVE-2022-23305]
  34. GitHub: https://github.com/thl-cmk/CVE-log4j-check_mk-plugin
    [CVE-2022-23305]
  35. GitHub: https://github.com/whitesource/log4j-detect-distribution
    [CVE-2022-23305]
  36. GitHub: https://github.com/AlphabugX/CVE-2022-23307
    [CVE-2022-23307: ![image](https://user-images.githubusercontent.com/27001865/150348452-38595c7d-8f16-4 ...]
  37. GitHub: https://github.com/HynekPetrak/log4shell-finder
    [CVE-2022-23307]
  38. GitHub: https://github.com/apache/logging-log4j1
    [CVE-2022-23307]
  39. GitHub: https://github.com/buluma/ansible-role-cve_2022-23307
    [CVE-2022-23307: Check and report for cve_2022_23307 (log4shell) on your system.]
  40. GitHub: https://github.com/cybersheepdog/Analyst-Tool
    [CVE-2022-23307]
  41. GitHub: https://github.com/davejwilson/azure-spark-pools-log4j
    [CVE-2022-23307]
  42. GitHub: https://github.com/logpresso/CVE-2021-44228-Scanner
    [CVE-2022-23307]
  43. GitHub: https://github.com/ltslog/ltslog
    [CVE-2022-23307]
  44. GitHub: https://github.com/thl-cmk/CVE-log4j-check_mk-plugin
    [CVE-2022-23307]
  45. GitHub: https://github.com/whitesource/log4j-detect-distribution
    [CVE-2022-23307]
  46. GitHub: https://github.com/Schnitker/log4j-min
    [CVE-2021-4104: Log4j 1.2 project, stripped of the additional appenders and CVEs that cause problems ...]
  47. GitHub: https://github.com/Schnitker/log4j-min
    [CVE-2022-23302: Log4j 1.2 project, stripped of the additional appenders and CVEs that cause problems ...]
  48. GitHub: https://github.com/AlphabugX/CVE-2022-23305
    [CVE-2022-23305: ![image](https://user-images.githubusercontent.com/27001865/150348452-38595c7d-8f16-4 ...]
  49. GitHub: https://github.com/HynekPetrak/log4shell-finder
    [CVE-2022-23305: Fastest filesystem scanner for log4shell (CVE-2021-44228, CVE-2021-45046) and other ...]
  50. GitHub: https://github.com/Schnitker/log4j-min
    [CVE-2022-23305: Log4j 1.2 project, stripped of the additional appenders and CVEs that cause problems ...]
  51. GitHub: https://github.com/Schnitker/log4j-min
    [CVE-2022-23307: Log4j 1.2 project, stripped of the additional appenders and CVEs that cause problems ...]

Before running any exploit against any system, make sure you are authorized by the owner of the target system(s) to perform such activity. In any other case, this would be considered as an illegal activity.

WARNING: Beware of using unverified exploits from sources such as GitHub or Exploit-DB. These exploits and PoCs could contain malware. For more information, see how to use exploits safely.

Risk Information


CVSS Score Source [?]: CVE-2022-23307
CVSS V2 Vector: AV:N/AC:L/Au:S/C:C/I:C/A:C/E:U/RL:OF/RC:C
CVSS Base Score:9.0 (High)
Impact Subscore:10.0
Exploitability Subscore:8.0
CVSS Temporal Score:6.7 (Medium)
CVSS Environmental Score:NA (None)
Modified Impact Subscore:NA
Overall CVSS Score:6.7 (Medium)
CVSS V3 Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CVSS Base Score:8.8 (High)
Impact Subscore:5.9
Exploitability Subscore:2.8
CVSS Temporal Score:7.7 (High)
CVSS Environmental Score:NA (None)
Modified Impact Subscore:NA
Overall CVSS Score:7.7 (High)
STIG Severity [?]: I
STIG Risk Rating: High

Go back to menu.

Plugin Source


This is the debian_DLA-2905.nasl nessus plugin source code. This script is Copyright (C) 2022 and is owned by Tenable, Inc. or an Affiliate thereof.

#%NASL_MIN_LEVEL 70300
#
# (C) Tenable Network Security, Inc.
#
# The descriptive text and package checks in this plugin were
# extracted from Debian Security Advisory dla-2905. The text
# itself is copyright (C) Software in the Public Interest, Inc.
#

include('deprecated_nasl_level.inc');
include('compat.inc');

if (description)
{
  script_id(157261);
  script_version("1.3");
  script_set_attribute(attribute:"plugin_modification_date", value:"2022/04/26");

  script_cve_id(
    "CVE-2021-4104",
    "CVE-2022-23302",
    "CVE-2022-23305",
    "CVE-2022-23307"
  );
  script_xref(name:"IAVA", value:"2021-A-0573");

  script_name(english:"Debian DLA-2905-1 : apache-log4j1.2 - LTS security update");

  script_set_attribute(attribute:"synopsis", value:
"The remote Debian host is missing one or more security-related updates.");
  script_set_attribute(attribute:"description", value:
"The remote Debian 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the
dla-2905 advisory.

  - 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)

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

  - 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)

  - 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)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version
number.");
  script_set_attribute(attribute:"see_also", value:"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004482");
  # https://security-tracker.debian.org/tracker/source-package/apache-log4j1.2
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?0db5f187");
  script_set_attribute(attribute:"see_also", value:"https://www.debian.org/lts/security/2022/dla-2905");
  script_set_attribute(attribute:"see_also", value:"https://security-tracker.debian.org/tracker/CVE-2021-4104");
  script_set_attribute(attribute:"see_also", value:"https://security-tracker.debian.org/tracker/CVE-2022-23302");
  script_set_attribute(attribute:"see_also", value:"https://security-tracker.debian.org/tracker/CVE-2022-23305");
  script_set_attribute(attribute:"see_also", value:"https://security-tracker.debian.org/tracker/CVE-2022-23307");
  script_set_attribute(attribute:"see_also", value:"https://packages.debian.org/source/stretch/apache-log4j1.2");
  script_set_attribute(attribute:"solution", value:
"Upgrade the apache-log4j1.2 packages.

For Debian 9 stretch, these problems have been fixed in version 1.2.17-7+deb9u2.");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:L/Au:S/C:C/I:C/A:C");
  script_set_cvss_temporal_vector("CVSS2#E:U/RL:OF/RC:C");
  script_set_cvss3_base_vector("CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H");
  script_set_cvss3_temporal_vector("CVSS:3.0/E:U/RL:O/RC:C");
  script_set_attribute(attribute:"cvss_score_source", value:"CVE-2022-23307");

  script_set_attribute(attribute:"exploitability_ease", value:"No known exploits are available");
  script_set_attribute(attribute:"exploit_available", value:"false");

  script_set_attribute(attribute:"vuln_publication_date", value:"2021/12/14");
  script_set_attribute(attribute:"patch_publication_date", value:"2022/01/31");
  script_set_attribute(attribute:"plugin_publication_date", value:"2022/01/31");

  script_set_attribute(attribute:"plugin_type", value:"local");
  script_set_attribute(attribute:"cpe", value:"p-cpe:/a:debian:debian_linux:liblog4j1.2-java");
  script_set_attribute(attribute:"cpe", value:"p-cpe:/a:debian:debian_linux:liblog4j1.2-java-doc");
  script_set_attribute(attribute:"cpe", value:"cpe:/o:debian:debian_linux:9.0");
  script_set_attribute(attribute:"stig_severity", value:"I");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_family(english:"Debian Local Security Checks");

  script_copyright(english:"This script is Copyright (C) 2022 and is owned by Tenable, Inc. or an Affiliate thereof.");

  script_dependencies("ssh_get_info.nasl");
  script_require_keys("Host/local_checks_enabled", "Host/Debian/release", "Host/Debian/dpkg-l");

  exit(0);
}

include('audit.inc');
include('debian_package.inc');

if (!get_kb_item("Host/local_checks_enabled")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);
if (!get_kb_item("Host/Debian/dpkg-l")) audit(AUDIT_PACKAGE_LIST_MISSING);

var release = get_kb_item('Host/Debian/release');
if ( isnull(release) ) audit(AUDIT_OS_NOT, 'Debian');
var release = chomp(release);
if (! preg(pattern:"^(9)\.[0-9]+", string:release)) audit(AUDIT_OS_NOT, 'Debian 9.0', 'Debian ' + release);
var cpu = get_kb_item('Host/cpu');
if (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);
if ('x86_64' >!< cpu && cpu !~ "^i[3-6]86$" && 'aarch64' >!< cpu) audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, 'Debian', cpu);

var pkgs = [
    {'release': '9.0', 'prefix': 'liblog4j1.2-java', 'reference': '1.2.17-7+deb9u2'},
    {'release': '9.0', 'prefix': 'liblog4j1.2-java-doc', 'reference': '1.2.17-7+deb9u2'}
];

var flag = 0;
foreach package_array ( pkgs ) {
  var release = NULL;
  var prefix = NULL;
  var reference = NULL;
  if (!empty_or_null(package_array['release'])) release = package_array['release'];
  if (!empty_or_null(package_array['prefix'])) prefix = package_array['prefix'];
  if (!empty_or_null(package_array['reference'])) reference = package_array['reference'];
  if (release && prefix && reference) {
    if (deb_check(release:release, prefix:prefix, reference:reference)) flag++;
  }
}

if (flag)
{
  security_report_v4(
    port       : 0,
    severity   : SECURITY_HOLE,
    extra      : deb_report_get()
  );
  exit(0);
}
else
{
  var tested = deb_pkg_tests_get();
  if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);
  else audit(AUDIT_PACKAGE_NOT_INSTALLED, 'liblog4j1.2-java / liblog4j1.2-java-doc');
}

The latest version of this script can be found in these locations depending on your platform:

  • Linux / Unix:
    /opt/nessus/lib/nessus/plugins/debian_DLA-2905.nasl
  • Windows:
    C:\ProgramData\Tenable\Nessus\nessus\plugins\debian_DLA-2905.nasl
  • Mac OS X:
    /Library/Nessus/run/lib/nessus/plugins/debian_DLA-2905.nasl

Go back to menu.

How to Run


Here is how to run the Debian DLA-2905-1 : apache-log4j1.2 - LTS security update as a standalone plugin via the Nessus web user interface (https://localhost:8834/):

  1. Click to start a New Scan.
  2. Select Advanced Scan.
  3. Navigate to the Plugins tab.
  4. On the top right corner click to Disable All plugins.
  5. On the left side table select Debian Local Security Checks plugin family.
  6. On the right side table select Debian DLA-2905-1 : apache-log4j1.2 - LTS security update plugin ID 157261.
  7. Specify the target on the Settings tab and click to Save the scan.
  8. Run the scan.

Here are a few examples of how to run the plugin in the command line. Note that the examples below demonstrate the usage on the Linux / Unix platform.

Basic usage:

/opt/nessus/bin/nasl debian_DLA-2905.nasl -t <IP/HOST>

Run the plugin with audit trail message on the console:

/opt/nessus/bin/nasl -a debian_DLA-2905.nasl -t <IP/HOST>

Run the plugin with trace script execution written to the console (useful for debugging):

/opt/nessus/bin/nasl -T - debian_DLA-2905.nasl -t <IP/HOST>

Run the plugin with using a state file for the target and updating it (useful for running multiple plugins on the target):

/opt/nessus/bin/nasl -K /tmp/state debian_DLA-2905.nasl -t <IP/HOST>

Go back to menu.

References


IAVA | Information Assurance Vulnerability Alert:
  • 2021-A-0573
See also: Similar and related Nessus plugins:
  • 156206 - Oracle Linux 7 : log4j (ELSA-2021-5206)
  • 156240 - CentOS 7 : log4j (CESA-2021:5206)
  • 156261 - RHEL 7 : rh-maven36-log4j12 (RHSA-2021:5269)
  • 156276 - openSUSE 15 Security Update : log4j12 (openSUSE-SU-2021:1612-1)
  • 156340 - openSUSE 15 Security Update : kafka (openSUSE-SU-2021:1631-1)
  • 156712 - Ubuntu 18.04 LTS / 20.04 LTS / 21.04 / 21.10 : Apache Log4j 1.2 vulnerability (USN-5223-1)
  • 156860 - Apache Log4j 1.x Multiple Vulnerabilities
  • 156871 - Amazon Linux AMI : log4j (ALAS-2022-1562)
  • 157127 - Oracle WebLogic Server (Jan 2022 CPU)
  • 157137 - Oracle Linux 6 : log4j (ELSA-2022-9056)
  • 157154 - SUSE SLES11 Security Update : log4j (SUSE-SU-2022:14881-1)
  • 157159 - Oracle Linux 8 : parfait:0.5 (ELSA-2022-0290)
  • 157214 - SUSE SLES15 Security Update : log4j (SUSE-SU-2022:0214-1)
  • 157221 - SUSE SLED12 / SLES12 Security Update : log4j (SUSE-SU-2022:0212-1)
  • 157225 - openSUSE 15 Security Update : log4j (openSUSE-SU-2022:0214-1)
  • 157232 - openSUSE 15 Security Update : log4j12 (openSUSE-SU-2022:0226-1)
  • 157233 - SUSE SLED15 / SLES15 Security Update : log4j12 (SUSE-SU-2022:0226-1)
  • 157374 - RHEL 7 : Red Hat JBoss Enterprise Application Platform 6.4 (RHSA-2022:0438)
  • 157375 - RHEL 7 : rh-maven36-log4j12 (RHSA-2022:0439)
  • 157376 - RHEL 8 : Red Hat JBoss Enterprise Application Platform 7.4 (RHSA-2022:0436)
  • 157417 - RHEL 7 : log4j (RHSA-2022:0442)
  • 157418 - RHEL 7 : Red Hat Single Sign-On 7.5.1 security update on RHEL 7 (Important) (RHSA-2022:0447)
  • 157452 - CentOS 7 : log4j (CESA-2022:0442)
  • 157455 - RHEL 8 : Red Hat Single Sign-On 7.5.1 security update on RHEL 8 (Important) (RHSA-2022:0448)
  • 157854 - RHEL 8 : RHV Manager (ovirt-engine) security update [ovirt-4.4.10-1] (Low) (RHSA-2022:0475)
  • 157904 - RHEL 8 : parfait:0.5 (RHSA-2022:0290)
  • 158057 - RHEL 7 : Red Hat JBoss Web Server 3.1 Service Pack 14 Security Update (Low) (RHSA-2022:0524)
  • 158101 - Oracle Linux 7 : log4j (ELSA-2022-0442)
  • 158150 - openSUSE 15 Security Update : kafka (openSUSE-SU-2022:0038-1)
  • 158210 - Amazon Linux 2 : log4j (ALAS-2022-1750)
  • 158462 - EulerOS 2.0 SP5 : log4j (EulerOS-SA-2022-1276)
  • 158832 - AlmaLinux 8 : parfait:0.5 (ALSA-2022:0290)
  • 159006 - Scientific Linux Security Update : log4j on SL6.x, SL7.x i686/x86_64 (2021:5206)
  • 159087 - EulerOS 2.0 SP5 : log4j (EulerOS-SA-2022-1330)

Version


This page has been produced using Nessus Professional 10.1.2 (#68) LINUX, Plugin set 202205072148.
Plugin file debian_DLA-2905.nasl version 1.3. For more plugins, visit the Nessus Plugin Library.

Go back to menu.