# CVE-2020-0543: Information disclosure in Intel(R) Processors > Incomplete cleanup in Intel processors allows authenticated local users to disclose sensitive information. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 15 Jun 2020 - **Updated:** 4 Aug 2024 - **Also known as:** ALPINE-CVE-2020-0543, DEBIAN-CVE-2020-0543, GHSA-8gvr-7c6p-jfwg, SUSE-SU-2020:1609-1, SUSE-SU-2020:1632-1, SUSE-SU-2020:1633-1, SUSE-SU-2021:1497-1, UBUNTU-CVE-2020-0543, openSUSE-SU-2020:0818-1, openSUSE-SU-2024:11369-1 ## What is CVE-2020-0543? CVE-2020-0543 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 15 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Incomplete cleanup from specific special register read operations in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access. Weakness: CWE-459 (Incomplete Cleanup) ## Which versions are affected by CVE-2020-0543? It affects 694 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `sca-patterns-sle11` | SUSE:Enterprise Storage 6 | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 1.3.1-7.6.1 | | `xen` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 4.12.3_02-3.18.1 | | `xen` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 4.12.3_02-3.18.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise Module for Server Applications 15 SP2 | All versions | 1.3.1-7.6.1 | | `xen` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 4.11.4_02-2.26.1 | | `xen` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.12.3_02-3.14.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 1.3.1-7.6.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 4.11.4_02-2.26.1 | | `xen` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.12.3_02-3.14.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 1.3.1-7.6.1 | | `xen` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 4.11.4_02-2.26.1 | | `xen` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 4.12.3_02-3.14.1 | | `sca-patterns-sle11` | SUSE:Manager Proxy 4.0 | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Manager Retail Branch Server 4.0 | All versions | 1.3.1-7.6.1 | | `sca-patterns-sle11` | SUSE:Manager Server 4.0 | All versions | 1.3.1-7.6.1 | | `xen` | openSUSE:Leap 15.1 | All versions | 4.12.3_02-lp151.2.18.2 | | `sca-patterns-sle11` | openSUSE:Tumbleweed | All versions | 1.3.5-1.2 | Products: Canonical Ubuntu Linux, Fedoraproject Fedora, Intel Celeron 1000m, Intel Celeron 1005m, Intel Celeron 1007u, Intel Celeron 1017u, Intel Celeron 1019y, Intel Celeron 1020e, Intel Celeron 1020m, Intel Celeron 1037u, Intel Celeron 1047ue, Intel Celeron 2955u, Intel Celeron 2957u, Intel Celeron 2970m, Intel Celeron 2980u, Intel Celeron 2981u, Intel Celeron 3755u, Intel Celeron 3765u, Intel Celeron 3855u, Intel Celeron 3865u and 674 more. ## How do I fix CVE-2020-0543? Apply the vendor's patch. ## Is CVE-2020-0543 being exploited? There is no known exploitation of CVE-2020-0543 in the wild and no public exploit code. ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild) - [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild) - [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild) - [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-0543 and fix it if it is affected. What it is: CVE-2020-0543 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 15 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-0543 in the wild and no public exploit code. Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-0543/ (Markdown: https://insights.sbomify.com/CVE-2020-0543/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-0543 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-0543 - OSV: https://osv.dev/vulnerability/CVE-2020-0543 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-0543/ Summaries are generated and may contain mistakes; the official description above is the record.