SUSE: Security Advisory (SUSE-SU-2021:2423-1)

Published: 2021-07-22 02:21:52
CVE Author: NIST National Vulnerability Database

CVSS Base Vector:



severity_date=2021-07-22 02:21:32 +0000 (Thu, 22 Jul 2021)

The remote host is missing an update for the 'systemd' Linux Distribution Package(s) announced via the SUSE-SU-2021:2423-1 advisory.

Detection Method:
Checks if a vulnerable Linux Distribution Package version is present on the target host.

Technical Details:
This update for systemd fixes the following issues: Security issues fixed: CVE-2021-33910: Fixed a denial of service (stack exhaustion) in systemd (PID 1) (bsc#1188063) Other fixes: mount-util: shorten the loop a bit (#7545) mount-util: do not use the official MAX_HANDLE_SZ (#7523) mount-util: tape over name_to_handle_at() flakiness (#7517) (bsc#1184761) mount-util: fix bad indenting mount-util: EOVERFLOW might have other causes than buffer size issues mount-util: fix error propagation in fd_fdinfo_mnt_id() mount-util: drop exponential buffer growing in name_to_handle_at_loop() udev: port udev_has_devtmpfs() to use path_get_mnt_id() mount-util: add new path_get_mnt_id() call that queries the mnt ID of a path mount-util: add name_to_handle_at_loop() wrapper around name_to_handle_at() mount-util: accept that name_to_handle_at() might fail with EPERM (#5499) basic: fallback to the fstat if we don't have access to the /proc/self/fdinfo sysusers: use the usual comment style test/TEST-21-SYSUSERS: add tests for new functionality sysusers: allow admin/runtime overrides to command-line config basic/strv: add function to insert items at position sysusers: allow the shell to be specified sysusers: move various user credential validity checks to src/basic/ man: reformat table in sysusers.d(5) sysusers: take configuration as positional arguments sysusers: emit a bit more info at debug level when locking fails sysusers: allow force reusing existing user/group IDs (#8037) sysusers: ensure GID in uid:gid syntax exists sysusers: make ADD_GROUP always create a group test: add TEST-21-SYSUSERS test sysuser: use OrderedHashmap sysusers: allow uid:gid in sysusers.conf files sysusers: fix memleak (#4430) These commits implement the option '--replace' for systemd-sysusers so %sysusers_create_Linux Distribution Package can be introduced in SLE and Linux Distribution Packages can rely on this rpm macro without wondering whether the macro is available on the different target the Linux Distribution Package is submitted to. Expect 644 permissions for /usr/lib/udev/compat-symlink-generation (bsc#1185807) systemctl: add --value option execute: make sure to call into PAM after initializing resource limits (bsc#1184967) rlimit-util: introduce setrlimit_closest_all() system-conf: drop reference to ShutdownWatchdogUsec= core: rename ShutdownWatchdogSec to RebootWatchdogSec (bsc#1185331) Return -EAGAIN instead of -EALREADY from unit_reload (bsc#1185046) rules: don't ignore Xen virtual interfaces anymore (bsc#1178561) write_net_rules: set execute bits (bsc#1178561) udev: rework network device renaming Revert 'Revert 'udev: network device renaming - immediately give up if the target name isn't available''

Affected Versions:
'systemd' Linux Distribution Package(s) on SUSE OpenStack Cloud Crowbar 9, SUSE OpenStack Cloud Crowbar 8, SUSE OpenStack Cloud 9, SUSE OpenStack Cloud 8, SUSE Linux Enterprise Server for SAP 12-SP4, SUSE Linux Enterprise Server for SAP 12-SP3, SUSE Linux Enterprise Server 12-SP4, SUSE Linux Enterprise Server 12-SP3, SUSE Linux Enterprise Server 12-SP2, HPE Helion Openstack 8.

Please install the updated Linux Distribution Package(s).

Solution Type:
Vendor Patch

Detection Type:
Linux Distribution Package

NIST (National Institute of Standards and Technology) NVD (National Vulnerability Database)


CVSS Score
SuSE Local Security Checks

Free Vulnerability Scanning, Assessment and Management

Mageni's Platform is packed with all the features you need to scan, assess and manage vulnerabilities like this - it is free, open source, lightning fast, reliable and scalable.


Frequently Asked Questions

No, you can scan concurrently as many assets as you want. Please note that you must be aware of the hardware requeriments of the platform to ensure a good performance.

No, you can add as many assest as you want. It doesn't matters if you have millions of assets, we won't charge you for that.

No. The software is completely free. We have no intention to charge you to use the software, in fact - it completely goes against our beliefs and business model.

A vulnerability is defined in the ISO 27002 standard as “A weakness of an asset or group of assets that can be exploited by one or more threats” (International Organization for Standardization, 2005)

We generate revenue by providing support and other services for customers that require a subscription so they get guaranteed support and enterprise services. To use Mageni's Platform is completely free, with no limits at all.

Yes. Mageni understands that there are professionals and businesses that need commercial support so Mageni provides an active support subscription with everything needed to run Mageni's Platform reliably and securely. More than software, it's access to security experts, knowledge resources, security updates, and support tools you can't get anywhere else. The subscription includes:

  • Ongoing delivery
    • Patches
    • Bug fixes
    • Updates
    • Upgrades
  • Technical support
    • 24/7 availability
    • Unlimited Incidents
    • Specialty-based routing
    • Multi-Channel
  • Commitments
    • Software certifications
    • Software assurance
    • SLA

No, we don't store the information of your vulnerabilities in our servers.

Vulnerability management is the process in which vulnerabilities in IT are identified and the risks of these vulnerabilities are evaluated. This evaluation leads to correcting the vulnerabilities and removing the risk or a formal risk acceptance by the management of an organization. The term vulnerability management is often confused with vulnerability scanning. Despite the fact both are related, there is an important difference between the two. Vulnerability scanning consists of using a computer program to identify vulnerabilities in networks, computer infrastructure or applications. Vulnerability management is the process surrounding vulnerability scanning, also taking into account other aspects such as risk acceptance, remediation etc. Source: "Implementing a Vulnerability Management Process". SANS Institute.

I am ready to start scanning for vulnerabilities