FERRAMENTAS LINUX: Critical Security Update for GDM: CVE-2025-6018 Vulnerability Patch

quinta-feira, 19 de junho de 2025

Critical Security Update for GDM: CVE-2025-6018 Vulnerability Patch

 

 

SUSE



SUSE has released a critical security update for GDM addressing CVE-2025-6018 (CVSS 8.6), removing pam_env from authentication stacks. Affects multiple enterprise Linux distributions including SLES 15 SP3 and SAP applications. Learn patch instructions and security implications.


Overview of the Security Advisory

SUSE has released an important security update addressing CVE-2025-6018 in the GNOME Display Manager (GDM), affecting multiple enterprise Linux distributions. 

This vulnerability, rated with a CVSS v4.0 score of 8.6, presents significant security risks that demand immediate attention from system administrators.

The update, published on June 19, 2025, specifically modifies GDM's PAM (Pluggable Authentication Modules) configuration by removing pam_env from the authentication stack, a security measure designed to prevent potential privilege escalation and system compromise.

Affected Products

The security patch impacts these SUSE enterprise platforms:

  • SUSE Enterprise Storage 7.1

  • SUSE Linux Enterprise High Performance Computing 15 SP3 (including LTSS version)

  • SUSE Linux Enterprise Server 15 SP3 (including LTSS version)

  • SUSE Linux Enterprise Server for SAP Applications 15 SP3

Technical Analysis of CVE-2025-6018

Vulnerability Details

The CVE-2025-6018 vulnerability stems from the inclusion of pam_env in GDM's authentication stack. This PAM module, typically used for setting environment variables during user sessions, presents several security concerns when used in authentication contexts:

  1. Potential for privilege escalation: Environment variables could be manipulated to affect authentication behavior

  2. Configuration risks: System-wide environment settings might inadvertently impact authentication security

  3. Attack surface expansion: Additional complexity in the authentication chain increases potential attack vectors

Risk Assessment

The CVSS scoring reveals the severity of this vulnerability:

CVSS v4.0 Metrics:

  • Attack Vector (AV): Local (L)

  • Attack Complexity (AC): Low (L)

  • Privileges Required (PR): None (N)

  • User Interaction (UI): None (N)

  • Impact Metrics: High confidentiality (VC:H), High integrity (VI:H), High availability (VA:H)

  • Final Score: 8.6 (High severity)

CVSS v3.1 Metrics:

  • Base Score: 8.4 (High severity)

  • Impact Subscore: 5.9

  • Exploitability Subscore: 2.5

Patch Implementation Guide

Installation Methods

System administrators have multiple options to apply this critical security update:

  1. Recommended Methods:

    • YaST online_update

    • zypper patch command

  2. Product-Specific Commands:

    bash
    # For SUSE Linux Enterprise High Performance Computing LTSS 15 SP3
    zypper in -t patch SUSE-SLE-Product-HPC-15-SP3-LTSS-2025-2015=1
    
    # For SUSE Linux Enterprise Server 15 SP3 LTSS
    zypper in -t patch SUSE-SLE-Product-SLES-15-SP3-LTSS-2025-2015=1
    
    # For SUSE Linux Enterprise Server for SAP Applications 15 SP3
    zypper in -t patch SUSE-SLE-Product-SLES_SAP-15-SP3-2025-2015=1
    
    # For SUSE Enterprise Storage 7.1
    zypper in -t patch SUSE-Storage-7.1-2025-2015=1

Updated Package Versions

The security update upgrades GDM to version 3.34.1-150200.8.26.1, including these components:

Core Packages:

  • gdm-3.34.1-150200.8.26.1

  • libgdm1-3.34.1-150200.8.26.1

  • typelib-1_0-Gdm-1_0-3.34.1-150200.8.26.1

Supporting Packages:

  • Debug information packages (gdm-debuginfolibgdm1-debuginfo)

  • Development files (gdm-devel)

  • Additional components (gdmflexiservergdm-systemdgdm-lang)

Security Best Practices for Enterprise Environments

Immediate Actions

  1. Prioritize patching for all affected systems, especially those:

    • Exposed to multiple users

    • Handling sensitive data

    • Part of critical infrastructure

  2. Verify successful installation:

    bash
    rpm -q gdm --changelog | grep CVE-2025-6018
  3. Review authentication logs for any suspicious activity pre-patch:

    bash
    journalctl -u gdm --since "2025-06-01"

Long-term Security Considerations

  1. Implement regular vulnerability scanning using tools like:

    • OpenSCAP

    • SUSE Manager

    • Third-party vulnerability management solutions

  2. Enhance PAM configuration:

    • Review all PAM stacks for similar issues

    • Consider implementing additional security modules like pam_faillock

  3. Monitor for security updates through:

    • SUSE Customer Center

    • Security mailing lists

    • Automated patch management systems

Impact Analysis for Different Deployment Scenarios

Enterprise Server Environments

For standard server installations, the risk is somewhat mitigated by:

  • Typically lower numbers of interactive users

  • More controlled access patterns
    However, patching remains critical for compliance and security hygiene.

High Performance Computing Clusters

HPC environments face particular challenges because:

  • Multiple users often share systems

  • Complex authentication chains may exist

  • Performance requirements sometimes delay patching

SAP Application Servers

SAP environments require special consideration due to:

  • Critical business functions

  • Complex authentication requirements

  • Potential regulatory compliance implications

Frequently Asked Questions

Q: Is this vulnerability being actively exploited?
A: As of the advisory date, there are no reports of active exploitation. However, the high CVSS score suggests immediate patching is warranted.

Q: Can this vulnerability be exploited remotely?

A: No, the attack vector is local (AV:L), requiring access to the system console or a local session.

Q: What are the potential consequences of not applying this patch?

A: Unpatched systems could allow authenticated users to escalate privileges or manipulate the authentication process through environment variables.

Q: Are workarounds available if immediate patching isn't possible?

A: Administrators could manually modify the PAM configuration to remove pam_env from the auth stack, but patching is the recommended solution.

Q: Does this affect non-SUSE distributions?

A: While this advisory is SUSE-specific, other distributions using similar GDM/PAM configurations should review their implementations.

Additional Resources

For further technical details and reference:

Nenhum comentário:

Postar um comentário