SUSE-RU-2023:4633-1: Recommended update for scap-security-guide
This update for scap-security-guide fixes the following issues: scap-security-guide was updated to 0.1.70 (jsc#ECO-3319) Add openembedded distro support Remove DRAFT wording for OpenShift STIG Remove test-function-checkplaybookfileremovedandadded test scap-security-guide: Add Poky support Also various SUSE profile bug fixes have been applied.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
suse/scap-security-guide-ubuntuto a version that resolves this vulnerability.Fixed in 0.1.70-150000.1.69.1 - Upgrade
Upgrade
suse/scap-security-guideto a version that resolves this vulnerability.Fixed in 0.1.70-150000.1.69.1 - Upgrade
Upgrade
suse/scap-security-guide-redhatto a version that resolves this vulnerability.Fixed in 0.1.70-150000.1.69.1 - Upgrade
Upgrade
suse/scap-security-guide-debianto a version that resolves this vulnerability.Fixed in 0.1.70-150000.1.69.1 - Upgrade
Upgrade
scap-security-guideto a version that resolves this vulnerability.Fixed in 0.1.70 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Manager-Tools-For-Micro-5-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Module-Basesystem-15-SP4-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Module-Basesystem-15-SP5-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-HPC-15-SP1-LTSS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-HPC-15-SP2-LTSS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-HPC-15-SP3-ESPOS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-HPC-15-SP3-LTSS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SLES-15-SP1-LTSS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SLES-15-SP2-LTSS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SLES-15-SP3-LTSS-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SLES_SAP-15-SP1-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SLES_SAP-15-SP2-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SLES_SAP-15-SP3-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SUSE-Manager-Proxy-4.2-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SUSE-Manager-Retail-Branch-Server-4.2-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-SLE-Product-SUSE-Manager-Server-4.2-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch SUSE-Storage-7.1-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch openSUSE-SLE-15.4-2023-4633=1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch openSUSE-SLE-15.5-2023-4633=1
Event History
Frequently Asked Questions
Which deployments should be checked for this update?
Check systems using scap-security-guide or its Ubuntu, Red Hat, or Debian package variants, as well as SUSE Manager Proxy 4.2, SUSE Manager Retail Branch Server 4.2, SUSE Manager Server 4.2, and SUSE Enterprise Storage 7.1. The advisory does not provide a vulnerable-version range, but identifies 0.1.70 as the updated scap-security-guide version.
Does the advisory describe a known exploit or attacker requirements?
No. The provided advisory information does not identify a CVE, exploitation method, attacker prerequisites, or a default-configuration exposure scenario.