Suse Linux Enterprise Server 16 1
Monthly
sdbootutil on SUSE Linux Enterprise Server 16.1, SLES for NVIDIA 16.1, openSUSE Leap 16.1, and Tumbleweed creates a world-readable debug log at /var/log/sdbootutil.log, enabling any local user to read potentially sensitive information from it. This local information disclosure (CWE-732) requires that the debug log has been generated and contains secrets. No public exploit has been identified at time of analysis, and the issue is not known to be actively exploited.
Local unprivileged users on SUSE Linux Enterprise Server 16.1, SLES for NVIDIA 16.1, openSUSE Leap 16.1 and openSUSE Tumbleweed can read a PIN or key secret that SUSE tooling renders as a QR code, because the secret is passed to qrencode as a command-line argument and is therefore exposed in /proc/<pid>/cmdline while the process runs. Exploitation requires the attacker to already hold a local low-privileged account on the same host (PR:L) and to win a short timing race against the brief qrencode invocation (AC:H), so this is a confidentiality-only credential-disclosure issue of modest severity with little realistic exposure on single-user or tightly controlled systems. There is no public exploit identified at time of analysis, and no vendor-released fix version has been confirmed in the available data, though SUSE tracks the issue through its Bugzilla and CVE pages.
sdbootutil on SUSE Linux Enterprise Server 16.1, SLES for NVIDIA 16.1, openSUSE Leap 16.1, and Tumbleweed creates a world-readable debug log at /var/log/sdbootutil.log, enabling any local user to read potentially sensitive information from it. This local information disclosure (CWE-732) requires that the debug log has been generated and contains secrets. No public exploit has been identified at time of analysis, and the issue is not known to be actively exploited.
Local unprivileged users on SUSE Linux Enterprise Server 16.1, SLES for NVIDIA 16.1, openSUSE Leap 16.1 and openSUSE Tumbleweed can read a PIN or key secret that SUSE tooling renders as a QR code, because the secret is passed to qrencode as a command-line argument and is therefore exposed in /proc/<pid>/cmdline while the process runs. Exploitation requires the attacker to already hold a local low-privileged account on the same host (PR:L) and to win a short timing race against the brief qrencode invocation (AC:H), so this is a confidentiality-only credential-disclosure issue of modest severity with little realistic exposure on single-user or tightly controlled systems. There is no public exploit identified at time of analysis, and no vendor-released fix version has been confirmed in the available data, though SUSE tracks the issue through its Bugzilla and CVE pages.