CVE-2018-18537 json
The GLCKIo low-level driver in ASUS Aura Sync v1.07.22 and earlier exposes a path to write an arbitrary DWORD to an arbitrary address.
published 7y ago modified 4mo ago also EUVD-2018-10259
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
The GLCKIo low-level driver in ASUS Aura Sync v1.07.22 and earlier exposes a path to write an arbitrary DWORD to an arbitrary address.
Is CVE-2018-18537 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/150893/ASUS-Driver-Privilege-Escalation.html referenced PoC, tagged "exploit" by a source, unverified
- secureauth.com https://www.secureauth.com/labs/advisories/asus-drivers-elevation-privilege-vulnerabilities referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2018/Dec/34 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
References
-
packetstormsecurity.com
/files/150893/ASUS-Driver-Privilege-Escalation.html
exploit, third-party-advisory, vdb-entry
-
secureauth.com
/labs/advisories/asus-drivers-elevation-privilege-vulnerabilities
exploit, third-party-advisory
-
seclists.org
/fulldisclosure/2018/Dec/34
mailing-list, exploit, third-party-advisory
-
securityfocus.com
/bid/106250
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-18537
- NVD CVE-2018-18537
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.