PACKETSTORM

📄 Lenovo LegionSpace 1.7.11.2 Unquoted Service Path_PACKETSTORM:221751

Description

Lenovo LegionSpace version 1.7.11.2 suffers from an unquoted service path vulnerability...
Visit Original Source

Basic Information

ID PACKETSTORM:221751
Published May 21, 2026 at 00:00

Affected Product

Affected Versions # Exploit Title: Lenovo LegionSpace 1.7.11.2 - 'DAService' Unquoted Service Path
# Exploit Author: CENACIF-MX
# Discovery Date: 2025-12-04
# Vendor Homepage: https://support.lenovo.com/es/es/solutions/legion_space
# Tested Version: 1.7.11.2
# Vulnerability Type: Unquoted Service Path
# Tested on OS: Microsoft Windows 11 Enterprise x64 es
# Fix: Upgrade to Lenovo LegionSpace 1.8.12.13 or later
# CVE : N/A
# Disclosure Timeline
# | Date | Event |
# |------|-------|
# | 2025-12-04 | Vulnerability discovered |
# | 2025-12-04 | Vendor notified |
# | 2026-02-09 | New version |



# Step to discover Unquoted Service Path:

C:\>wmic service get name, pathname, displayname, startmode | findstr "Auto" | findstr /i /v "C:\Windows\\" | findstr /i "Lenovo" | findstr /i /v """



DAService DAService C:\Program Files\Lenovo\LegionSpace\1.7.11.2\LSDaemon.exe Auto



# Service info:

C:\>sc qc "DAService"
[SC] QueryServiceConfig CORRECTO

NOMBRE_SERVICIO: DAService
TIPO : 10 WIN32_OWN_PROCESS
TIPO_INICIO : 2 AUTO_START
CONTROL_ERROR : 1 NORMAL
NOMBRE_RUTA_BINARIO: C:\Program Files\Lenovo\LegionSpace\1.7.11.2\LSDaemon.exe
GRUPO_ORDEN_CARGA :
ETIQUETA : 0
NOMBRE_MOSTRAR : DAService
DEPENDENCIAS :
NOMBRE_INICIO_SERVICIO: LocalSystem

#Exploit:

A successful attempt would require the local user to be able to insert their code in the system root path undetected by the OS or other security applications where it could potentially be executed during application startup or reboot. If successful, the local user's code would execute with the elevated privileges of the application.

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.