Skip to content

Security: Execorn/aurora-greeter

Security

SECURITY.md

Security Policy

Supported Versions

Security fixes and updates are applied to the master branch and the latest tagged releases:

Version Supported
1.x Yes
< 1.0 No

Reporting a Vulnerability

Please do not disclose security vulnerabilities publicly in issues or discussions.

Use GitHub Private Vulnerability Reporting to submit a security advisory privately. Include a description of the issue, affected components, steps to reproduce, and any mitigation suggestions.

You can expect an initial response within 72 hours.

Security Architecture & Scope

Aurora Greeter executes as a display manager greeter under the non-privileged sddm user before user authentication:

  1. PAM Environment Sanitization: SDDM and PAM actively scrub environment variables before greeter initialization. Aurora Greeter injects GPU decoding flags strictly via SDDM's native [General] GreeterEnvironment= configuration in /etc/sddm.conf.d/.
  2. Filesystem Isolation: Persistent settings written by the greeter are restricted to /var/lib/sddm/.config/AuroraGreeter/ with mode 750 (sddm:sddm).
  3. Privilege Demarcation: System-level theme modifications via sddm-aurora-ctl check for root privileges (geteuid() == 0) and re-exec with sudo using direct argument arrays (os.execvp), preventing shell injection vulnerabilities.
  4. Media Sandboxing: Audio negotiation is redirected to a null sink (GST_AUDIOSINK=fakesink) to prevent non-privileged PipeWire daemon crashes inside greeter sessions.

There aren't any published security advisories