CVE-2020-0561
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user...
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
7.8
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
- Record
CVE-2020-0561- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 4.6 Medium
AV:L/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-665
- Updated
- 2026-11-02
CVE List No score
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
- Record
CVE-2020-0561- Updated
- 2026-11-02
EUVDEUVD-2020-2059 No score
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
- Record
EUVD-2020-2059- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-r4p7-pmgm-2v37 No score
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user...
Improper initialization in the Intel(R) SGX SDK before v2.6.100.1 may allow an authenticated user to potentially enable escalation of privilege via local access.
- Record
GHSA-r4p7-pmgm-2v37- Weakness
- CWE-665
- Updated
- 2026-11-02
OSVopenSUSE-SU-2020:0604-1 No score
Security update for chromium
This update for chromium fixes the following issues:
Chromium was updated to 81.0.4044.129 (boo#1170107):
- CVE-2020-0561: Fixed a use after free in storage
- CVE-2020-6462: Fixed a use after free in task scheduling
- CVE-2020-6459: Fixed a use after free in payments
- CVE-2020-6460: Fixed an insufficient data validation in URL formatting
- CVE-2020-6458: Fixed an out of bounds read and write in PDFium
- Record
openSUSE-SU-2020:0604-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2020:0615-1 No score
Security update for chromium
This update for chromium fixes the following issues:
Chromium was updated to 81.0.4044.129 (boo#1170107):
- CVE-2020-0561: Fixed a use after free in storage
- CVE-2020-6462: Fixed a use after free in task scheduling
- CVE-2020-6459: Fixed a use after free in payments
- CVE-2020-6460: Fixed an insufficient data validation in URL formatting
- CVE-2020-6458: Fixed an out of bounds read and write in PDFium
This update was imported from the openSUSE:Leap:15.1:Update update project.
- Record
openSUSE-SU-2020:0615-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10681-1 No score
chromedriver-93.0.4577.82-1.1 on GA media
These are all security issues fixed in the chromedriver-93.0.4577.82-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10681-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:12948-1 No score
ungoogled-chromium-113.0.5672.92-1.1 on GA media
These are all security issues fixed in the ungoogled-chromium-113.0.5672.92-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:12948-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
chromiumSUSE:Package Hub 15 SP1 |
before 81.0.4044.129-bp151.3.75.1 | 81.0.4044.129-bp151.3.75.1 |
chromiumopenSUSE:Leap 15.1 |
before 81.0.4044.129-bp151.3.75.1 | 81.0.4044.129-bp151.3.75.1 |
chromiumSUSE:Package Hub 15 SP1 |
before 81.0.4044.129-bp151.3.79.1 | 81.0.4044.129-bp151.3.79.1 |
chromiumopenSUSE:Tumbleweed |
before 93.0.4577.82-1.1 | 93.0.4577.82-1.1 |
chromiumopenSUSE:Tumbleweed |
before 113.0.5672.92-1.1 | 113.0.5672.92-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-0561 is a high vulnerability (CVSS 7.8) in Intel Software Guard Extensions Sdk, published February 13, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.41%, the 35th percentile. Fixed in chromium 81.0.4044.129-bp151.3.75.1.
References
intel.com/content/www/us/en/security-center/advisory/intel-sa-00336.html
lists.opensuse.org/opensuse-security-announce/2020-05/msg00009.html
lists.opensuse.org/opensuse-security-announce/2020-05/msg00014.html
nvd.nist.gov/vuln/detail/CVE-2020-0561
github.com/advisories/GHSA-r4p7-pmgm-2v37
lists.opensuse.org/archives/list/[email protected]/thread/HJ56OQK4ESIDWMRCE574AVEUBQ7O5ZPB
Show 194 moreShow less
bugzilla.suse.com/1170107
suse.com/security/cve/CVE-2020-0561
suse.com/security/cve/CVE-2020-6458
suse.com/security/cve/CVE-2020-6459
suse.com/security/cve/CVE-2020-6460
suse.com/security/cve/CVE-2020-6462
lists.opensuse.org/archives/list/[email protected]/thread/CISSJFTLJCZM6FLWTJJSQEDTEBDRTV6R
suse.com/security/cve/CVE-2017-11215
suse.com/security/cve/CVE-2017-11225
suse.com/security/cve/CVE-2017-15386
suse.com/security/cve/CVE-2017-15387
suse.com/security/cve/CVE-2017-15388
suse.com/security/cve/CVE-2017-15389
suse.com/security/cve/CVE-2017-15390
suse.com/security/cve/CVE-2017-15391
suse.com/security/cve/CVE-2017-15392
suse.com/security/cve/CVE-2017-15393
suse.com/security/cve/CVE-2017-15394
suse.com/security/cve/CVE-2017-15395
suse.com/security/cve/CVE-2017-15396
suse.com/security/cve/CVE-2017-15398
suse.com/security/cve/CVE-2017-15399
suse.com/security/cve/CVE-2017-15407
suse.com/security/cve/CVE-2017-15408
suse.com/security/cve/CVE-2017-15409
suse.com/security/cve/CVE-2017-15410
suse.com/security/cve/CVE-2017-15411
suse.com/security/cve/CVE-2017-15412
suse.com/security/cve/CVE-2017-15413
suse.com/security/cve/CVE-2017-15415
suse.com/security/cve/CVE-2017-15416
suse.com/security/cve/CVE-2017-15417
suse.com/security/cve/CVE-2017-15418
suse.com/security/cve/CVE-2017-15419
suse.com/security/cve/CVE-2017-15420
suse.com/security/cve/CVE-2017-15422
suse.com/security/cve/CVE-2017-15423
suse.com/security/cve/CVE-2017-15424
suse.com/security/cve/CVE-2017-15425
suse.com/security/cve/CVE-2017-15426
suse.com/security/cve/CVE-2017-15427
suse.com/security/cve/CVE-2017-15429
suse.com/security/cve/CVE-2017-15430
suse.com/security/cve/CVE-2017-5006
suse.com/security/cve/CVE-2017-5007
suse.com/security/cve/CVE-2017-5008
suse.com/security/cve/CVE-2017-5009
suse.com/security/cve/CVE-2017-5010
suse.com/security/cve/CVE-2017-5011
suse.com/security/cve/CVE-2017-5012
suse.com/security/cve/CVE-2017-5013
suse.com/security/cve/CVE-2017-5014
suse.com/security/cve/CVE-2017-5015
suse.com/security/cve/CVE-2017-5016
suse.com/security/cve/CVE-2017-5017
suse.com/security/cve/CVE-2017-5018
suse.com/security/cve/CVE-2017-5019
suse.com/security/cve/CVE-2017-5020
suse.com/security/cve/CVE-2017-5021
suse.com/security/cve/CVE-2017-5022
suse.com/security/cve/CVE-2017-5023
suse.com/security/cve/CVE-2017-5024
suse.com/security/cve/CVE-2017-5025
suse.com/security/cve/CVE-2017-5026
suse.com/security/cve/CVE-2017-5030
suse.com/security/cve/CVE-2017-5035
suse.com/security/cve/CVE-2017-5041
suse.com/security/cve/CVE-2017-5044
suse.com/security/cve/CVE-2017-5052
suse.com/security/cve/CVE-2017-5053
suse.com/security/cve/CVE-2017-5054
suse.com/security/cve/CVE-2017-5055
suse.com/security/cve/CVE-2017-5056
suse.com/security/cve/CVE-2017-5057
suse.com/security/cve/CVE-2017-5058
suse.com/security/cve/CVE-2017-5059
suse.com/security/cve/CVE-2017-5060
suse.com/security/cve/CVE-2017-5061
suse.com/security/cve/CVE-2017-5062
suse.com/security/cve/CVE-2017-5063
suse.com/security/cve/CVE-2017-5064
suse.com/security/cve/CVE-2017-5065
suse.com/security/cve/CVE-2017-5066
suse.com/security/cve/CVE-2017-5067
suse.com/security/cve/CVE-2017-5068
suse.com/security/cve/CVE-2017-5069
suse.com/security/cve/CVE-2017-5070
suse.com/security/cve/CVE-2017-5071
suse.com/security/cve/CVE-2017-5072
suse.com/security/cve/CVE-2017-5073
suse.com/security/cve/CVE-2017-5074
suse.com/security/cve/CVE-2017-5075
suse.com/security/cve/CVE-2017-5076
suse.com/security/cve/CVE-2017-5077
suse.com/security/cve/CVE-2017-5078
suse.com/security/cve/CVE-2017-5079
suse.com/security/cve/CVE-2017-5080
suse.com/security/cve/CVE-2017-5081
suse.com/security/cve/CVE-2017-5082
suse.com/security/cve/CVE-2017-5083
suse.com/security/cve/CVE-2017-5085
suse.com/security/cve/CVE-2017-5086
suse.com/security/cve/CVE-2017-5087
suse.com/security/cve/CVE-2017-5088
suse.com/security/cve/CVE-2017-5089
suse.com/security/cve/CVE-2017-5091
suse.com/security/cve/CVE-2017-5092
suse.com/security/cve/CVE-2017-5093
suse.com/security/cve/CVE-2017-5094
suse.com/security/cve/CVE-2017-5095
suse.com/security/cve/CVE-2017-5096
suse.com/security/cve/CVE-2017-5097
suse.com/security/cve/CVE-2017-5098
suse.com/security/cve/CVE-2017-5099
suse.com/security/cve/CVE-2017-5100
suse.com/security/cve/CVE-2017-5101
suse.com/security/cve/CVE-2017-5102
suse.com/security/cve/CVE-2017-5103
suse.com/security/cve/CVE-2017-5104
suse.com/security/cve/CVE-2017-5105
suse.com/security/cve/CVE-2017-5106
suse.com/security/cve/CVE-2017-5107
suse.com/security/cve/CVE-2017-5108
suse.com/security/cve/CVE-2017-5109
suse.com/security/cve/CVE-2017-5110
suse.com/security/cve/CVE-2017-5111
suse.com/security/cve/CVE-2017-5112
suse.com/security/cve/CVE-2017-5113
suse.com/security/cve/CVE-2017-5114
suse.com/security/cve/CVE-2017-5115
suse.com/security/cve/CVE-2017-5116
suse.com/security/cve/CVE-2017-5117
suse.com/security/cve/CVE-2017-5118
suse.com/security/cve/CVE-2017-5119
suse.com/security/cve/CVE-2017-5120
suse.com/security/cve/CVE-2017-5121
suse.com/security/cve/CVE-2017-5122
suse.com/security/cve/CVE-2017-5124
suse.com/security/cve/CVE-2017-5125
suse.com/security/cve/CVE-2017-5126
suse.com/security/cve/CVE-2017-5127
suse.com/security/cve/CVE-2017-5128
suse.com/security/cve/CVE-2017-5129
suse.com/security/cve/CVE-2017-5130
suse.com/security/cve/CVE-2017-5131
suse.com/security/cve/CVE-2017-5132
suse.com/security/cve/CVE-2017-5133
suse.com/security/cve/CVE-2017-7000
suse.com/security/cve/CVE-2018-16065
suse.com/security/cve/CVE-2018-16066
suse.com/security/cve/CVE-2018-16067
suse.com/security/cve/CVE-2018-16068
suse.com/security/cve/CVE-2018-16069
suse.com/security/cve/CVE-2018-16070
suse.com/security/cve/CVE-2018-16071
suse.com/security/cve/CVE-2018-16073
suse.com/security/cve/CVE-2018-16074
suse.com/security/cve/CVE-2018-16075
suse.com/security/cve/CVE-2018-16076
suse.com/security/cve/CVE-2018-16077
suse.com/security/cve/CVE-2018-16078
suse.com/security/cve/CVE-2018-16079
suse.com/security/cve/CVE-2018-16080
suse.com/security/cve/CVE-2018-16081
suse.com/security/cve/CVE-2018-16082
suse.com/security/cve/CVE-2018-16083
suse.com/security/cve/CVE-2018-16084
suse.com/security/cve/CVE-2018-16085
suse.com/security/cve/CVE-2018-16086
suse.com/security/cve/CVE-2018-16087
suse.com/security/cve/CVE-2018-16088
suse.com/security/cve/CVE-2018-17462
suse.com/security/cve/CVE-2018-17463
suse.com/security/cve/CVE-2018-17464
suse.com/security/cve/CVE-2018-17465
suse.com/security/cve/CVE-2018-17466
suse.com/security/cve/CVE-2018-17467
suse.com/security/cve/CVE-2018-17468
suse.com/security/cve/CVE-2018-17469
suse.com/security/cve/CVE-2018-17470
suse.com/security/cve/CVE-2018-17471
suse.com/security/cve/CVE-2018-17472
suse.com/security/cve/CVE-2018-17473
suse.com/security/cve/CVE-2018-17474
suse.com/security/cve/CVE-2018-17475
suse.com/security/cve/CVE-2018-17476
suse.com/security/cve/CVE-2018-17477
suse.com/security/cve/CVE-2018-17478
suse.com/security/cve/CVE-2018-17479
suse.com/security/cve/CVE-2018-17480
suse.com/security/cve/CVE-2018-17481
suse.com/security/cve/CVE-2018-18335
suse.com/security/cve/CVE-2018-18336
suse.com/security/cve/CVE-2018-18337
Left out here: 2,118 references. The JSON record has them.