Home
» Security vulnerabilities
» CVE-2020-15368
AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as demonstrated by triggering a triple fault via a request to zero CR3.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2020-15368
Conclusion & alert: CVE-2020-15368 is rated Moderate Risk (42.8/100) : CVSS Medium severity, with medium exploitation likelihood (EPSS 1.30%).Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2020-15368
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
3.73%
1.30%
-2.44%
2
2026-05-29
5.89%
3.73%
-2.16%
3
2026-05-12
—
5.89%
—
Full EPSS history
(23 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2020-15368
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
5.5
3.1
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
1.8
3.6
[email protected]
6.1
3.1
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8
4.2
134c704f-9b21-4f2e-91b3-4a467353bcc0
2.1
2.0
LOW
AV:L/AC:L/Au:N/C:N/I:P/A:N
Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
3.9
2.9
[email protected]
Weakness enumeration for CVE-2020-15368
GitHub Security Advisory for CVE-2020-15368
GHSA-7387-h76h-9m29 · Severity: low
— AsrDrv103.sys in the ASRock RGB Driver does not properly restrict access from user space, as...
Affected software / configurations for CVE-2020-15368
References for CVE-2020-15368
cvelogic
Threat Intelligence