- A security scientist discovered a big mistake in ASUS Driverhub
- The error allows users to run malicious code external
- A patch was already released
Driverhub, Asus’ official driver control tool, wore a critical vulnerability that allowed threat actors to perform malicious code on affected devices, externally. It was recently discovered and a patch was released so that users are encouraged to use it as soon as possible to mitigate potential risks.
Asus Driverhub is a piece of software that automatically downloads and installs the latest drivers for ASUs devices, including laptops, motherboards and peripheral devices. Its goal is to keep the devices up to date at all times without needing too much manual intervention. According to Bleeping computerDriverhub comes pre -installed on some devices and is constantly running in the background (which makes sense if it is to keep software updated at all times).
Now a security researcher with the alias Mrbruh said that Driverhub was suffering from poor validation of commands. This enabled him to link two vulnerabilities, now track as CVE-2025-3462 and CVE-2025-3463, and get the tool to run malicious software.
Releases the patch
He reported his conclusions on April 8, and Asus came back with a patch ten days later, April 18. Although the company says the error for the error is somewhat limited: “This question is limited to motherboards and does not affect laptops, desktop computers or other endpoints,” Asus said, describing CVE.
The “recommended” users still. “This update includes important security updates and ASUS strongly recommends that users update their Asus Driverhub installation to the latest version,” the company said in a security advice.
“The latest software update can be obtained by opening the ASUS Driverhub and then clicking the” Update NOW “button. Ironically, the tool that handles all driver installations must automatically be patched – manually.
According to cyberinsides, the vulnerability window has been open to “an indefinite period”, but since there are no reports of abuse in nature, it is safe to assume that Mrbruh was the first to see the error.
Via Bleeping computer
