CVE-2022-24139
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk28th percentile - higher than 28% of all known CVEs
Summary
In IOBit Advanced System Care (AscService.exe) version 15, an attacker with SEImpersonatePrivilege can create a named pipe with the same name as one of ASCService's pipes. During login, the service first tries to connect before creating the pipe, allowing the attacker to intercept the connection and escalate privileges.
Risk Assessment
The risk involves privilege escalation from ADMIN to SYSTEM or from local ADMIN to domain ADMIN, potentially leading to full system or domain compromise.
Recommendation
Immediately update IOBit Advanced System Care to the latest version and restrict SEImpersonatePrivilege for unauthorized users.
Other vulnerabilities in IOBit Advanced System Care
See all- CVE-2022-24140Medium
IObit products (Advanced System Care 15, iTop Screen Recorder 2.1, iTop VPN 3.2, Driver Booster 9, iTop Screenshot) use unencrypted HTTP connections to download configuration files during updates. An attacker can intercept this traffic and supply a malicious config file pointing to fake update locations, leading to remote code execution with administrative privileges.
- CVE-2022-24138High
A vulnerability in IOBit Advanced System Care 15 and Action Download Center allows low-privileged users to replace a genuine component with a malicious executable in the ProgramData folder, which has "rwx" permissions for all users. By using SetOpLock and waiting for CreateProcess, an attacker can achieve code execution with administrator privileges.
Original NVD description (English source)
In IOBit Advanced System Care (AscService.exe) 15, an attacker with SEImpersonatePrivilege can create a named pipe with the same name as one of ASCService's named pipes. ASCService first tries to connect before trying to create the named pipes, because of that during login the service will try to connect to the attacker which will lead to either escalation of privileges (through token manipulation and ImpersonateNamedPipeClient() ) from ADMIN -> SYSTEM or from Local ADMIN-> Domain ADMIN depending on the user and named pipe that is used.