Vulnerabilities / SUSE-SU-2021:2106-1

critical

SUSE-SU-2021:2106-1

Security update for salt

In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

No source gives a CVSS score.

Trivy's own label is CRITICAL. Rated critical by SUSE.

Description

This update for salt fixes the following issues: Update to Salt release version 3002.2 (jsc#ECO-3212, jsc#SLE-18033, jsc#SLE-18028) - Check if dpkgnotify is executable (bsc#1186674) - Drop support for Python2. Obsoletes `python2-salt` package (jsc#SLE-18028) - virt module updates * network: handle missing ipv4 netmask attribute * more network support * PCI/USB host devices passthrough support - Set distro requirement to oldest supported version in requirements/base.txt - Bring missing part of async batch implementation back (CVE-2021-25315, bsc#1182382) - Always require `python3-distro` (bsc#1182293) - Remove deprecated warning that breaks minion execution when 'server_id_use_crc' opts is missing - Fix pkg states when DEB package has 'all' arch - Do not force beacons configuration to be a list. - Remove msgpack < 1.0.0 from base requirements (bsc#1176293) - msgpack support for version >= 1.0.0 (bsc#1171257) - Fix issue parsing errors in ansiblegate state module - Prevent command injection in the snapper module (bsc#1185281, CVE-2021-31607) - transactional_update: detect recursion in the executor - Add subpackage salt-transactional-update (jsc#SLE-18033) - Improvements on 'ansiblegate' module (bsc#1185092): * New methods: ansible.targets / ansible.discover_playbooks - Add support for Alibaba Cloud Linux 2 (Aliyun Linux) - Regression fix of salt-ssh on processing targets - Update target fix for salt-ssh and avoiding race condition on salt-ssh event processing (bsc#1179831, bsc#1182281) - Add notify beacon for Debian/Ubuntu systems - Fix zmq bug that causes salt-call to freeze (bsc#1181368)

Affected packages and fixed versions

SourcePackageFixed in
SUSE Linux Enterprise 15.2python2-distro, python3-distro, python3-salt and 14 more1.5.0-3.5.1 and 1 more
SUSE Linux Enterprise 15.3python2-distro, python3-distro1.5.0-3.5.1
SUSE Linux Enterprise Micro 5.0python3-distro, python3-salt, salt and 2 more1.5.0-3.5.1 and 1 more
Show all 24 entries from 3 sources
SourcePackageFixed in
SUSE Linux Enterprise 15.2python2-distro1.5.0-3.5.1
SUSE Linux Enterprise 15.2python3-distro1.5.0-3.5.1
SUSE Linux Enterprise 15.2python3-salt3002.2-37.1
SUSE Linux Enterprise 15.2salt3002.2-37.1
SUSE Linux Enterprise 15.2salt-api3002.2-37.1
SUSE Linux Enterprise 15.2salt-bash-completion3002.2-37.1
SUSE Linux Enterprise 15.2salt-cloud3002.2-37.1
SUSE Linux Enterprise 15.2salt-doc3002.2-37.1
SUSE Linux Enterprise 15.2salt-fish-completion3002.2-37.1
SUSE Linux Enterprise 15.2salt-master3002.2-37.1
SUSE Linux Enterprise 15.2salt-minion3002.2-37.1
SUSE Linux Enterprise 15.2salt-proxy3002.2-37.1
SUSE Linux Enterprise 15.2salt-ssh3002.2-37.1
SUSE Linux Enterprise 15.2salt-standalone-formulas-configuration3002.2-37.1
SUSE Linux Enterprise 15.2salt-syndic3002.2-37.1
SUSE Linux Enterprise 15.2salt-transactional-update3002.2-37.1
SUSE Linux Enterprise 15.2salt-zsh-completion3002.2-37.1
SUSE Linux Enterprise 15.3python2-distro1.5.0-3.5.1
SUSE Linux Enterprise 15.3python3-distro1.5.0-3.5.1
SUSE Linux Enterprise Micro 5.0python3-distro1.5.0-3.5.1
SUSE Linux Enterprise Micro 5.0python3-salt3002.2-37.1
SUSE Linux Enterprise Micro 5.0salt3002.2-37.1
SUSE Linux Enterprise Micro 5.0salt-minion3002.2-37.1
SUSE Linux Enterprise Micro 5.0salt-transactional-update3002.2-37.1

References

All 20 references

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.