VYPR
Unrated severityNVD Advisory· Published May 20, 2022· Updated Aug 3, 2024

CVE-2022-27095

CVE-2022-27095

Description

BattlEye v0.9 contains an unquoted service path which allows attackers to escalate privileges to the system level.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

BattlEye 0.9's BEService has an unquoted service path allowing local privilege escalation to SYSTEM.

Vulnerability

BattlEye version 0.9 (and 0.94 as tested) contains an unquoted service path vulnerability in the BEService service. The service binary path is set to C:\Program Files (x86)\Common Files\BattlEye\BEService.exe without enclosing quotes [1]. This allows Windows to interpret spaces in the path as separators, potentially executing a different executable if placed in a preceding directory.

Exploitation

An attacker with local user access can exploit this by placing a malicious executable in a directory that Windows will search due to the unquoted path. For example, placing Program.exe in C:\ would cause Windows to execute it instead of the intended BEService.exe when the service starts. The attacker must have write access to such a directory and then trigger service start (e.g., via reboot or manual start). The service runs under the LocalSystem account, so the malicious code executes with SYSTEM privileges [1].

Impact

Successful exploitation results in local privilege escalation from a standard user to SYSTEM, granting full control over the affected Windows system. The attacker can then install programs, view/change data, or create new accounts with full user rights.

Mitigation

As of the publication date (March 2022), no official patch has been released by BattlEye. The recommended mitigation is to manually quote the service binary path in the Windows Registry or using sc config command: sc config BEService binPath="\"C:\Program Files (x86)\Common Files\BattlEye\BEService.exe\"". Additionally, ensure that untrusted users cannot write to directories in the unquoted path. This CVE is not listed in the Known Exploited Vulnerabilities catalog.

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.