CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2020-0110 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-0110?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-0110?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-0110 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| intel:jhl6540_firmware | before 1.41.1054.0 |
| intel:jhl6340_firmware | before 1.41.1054.0 |
| intel:jhl6240_firmware | before 1.41.1054.0 |
| intel:jhl7540_firmware | before 1.41.1054.0 |
| intel:jhl7440_firmware | before 1.41.1054.0 |
| intel:jhl7340_firmware | before 1.41.1054.0 |
| intel:jhl8540_firmware | before 1.41.1054.0 |
| intel:jhl8440_firmware | before 1.41.1054.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | linux | 5.5.13-1 | DEBIAN-CVE-2020-0110 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-aws-5.3 | 5.3.0-1017.18~18.04.1 | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-azure-5.3 | 5.3.0-1020.21~18.04.1 | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-azure, linux-aws-5.0 and 4 more | no fix listed | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-gcp-5.3, linux-gke-5.3 | 5.3.0-1018.19~18.04.1 | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-hwe | 5.3.0-51.44~18.04.2 | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-oracle-5.3 | 5.3.0-1016.18~18.04.1 | UBUNTU-CVE-2020-0110 |
| Ubuntu | 18.04:LTS | linux-raspi2-5.3 | 5.3.0-1023.25~18.04.1 | UBUNTU-CVE-2020-0110 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-raspi2 and 2 more | no fix listed | UBUNTU-CVE-2020-0110 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-realtime, linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2020-0110 |
| Ubuntu | 24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2020-0110 |
| openSUSE | Leap 15.2 | kernel-rt, kernel-syms-rt, kernel-rt_debug and 1 more | 5.3.18-lp152.3.5.1 | openSUSE-SU-2021:0242-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.
Red Hat rates this Low.
As the attacker must have the ability to write to these files, a possible mitigation would be to reduce the access that users and their processes would have to the files used in the attack. The files within the /proc/ filesystem can be temporarily modified with the chmod/chown command for each boot.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-alt | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise MRG 2 | kernel-rt | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-0110.