PatchTheCVEa-tuning vulnerabilities and fixes
Recent CVEs affecting a-tuning, with upgrade or downgrade steps. 4 tracked.
Also searched as: a tuning.
a-tuning has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2018-10-30. Highest priority: CVE-2018-10711 (score 51/100).
- CVE-2018-10712 HIGH 7.8 UPGRADE UPGRADE The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.
- CVE-2018-10711 HIGH 7.8 UPGRADE UPGRADE The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.
- CVE-2018-10710 HIGH 7.1 UPGRADE UPGRADE The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.
- CVE-2018-10709 HIGH 7.8 UPGRADE UPGRADE The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0.
FAQ
How do I fix a-tuning vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is a-tuning being exploited right now?
None of the tracked a-tuning CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which a-tuning CVE should I patch first?
CVE-2018-10711 currently ranks highest (51/100): The AsrDrv101.sys and AsrDrv102.sys low-level drivers in ASRock RGBLED before v1.0.35.1, A-Tuning before v3.0..