Google Asylo up to 0.6.0 sgx_params out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.5$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in Google Asylo up to 0.6.0. This issue affects the function sgx_params. Such manipulation leads to out-of-bounds. This vulnerability is uniquely identified as CVE-2020-8936. Local access is required to approach this attack. No exploit exists. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Google Asylo up to 0.6.0. Affected by this issue is the function sgx_params. The manipulation with an unknown input leads to a out-of-bounds vulnerability. Using CWE to declare the problem leads to CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality.

The weakness was disclosed 12/16/2020 as 83036fd841d33baa7e039f842d131aa7881fdcc2. The advisory is shared for download at github.com. This vulnerability is handled as CVE-2020-8936. There are known technical details, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.5
VulDB Meta Temp Score: 2.5

VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: github.com

Timelineinfo

02/12/2020 🔍
12/16/2020 +308 days 🔍
12/16/2020 +0 days 🔍
12/18/2020 +2 days 🔍

Sourcesinfo

Vendor: google.com
Product: github.com

Advisory: 83036fd841d33baa7e039f842d131aa7881fdcc2
Status: Not defined
Confirmation: 🔍

CVE: CVE-2020-8936 (🔍)
GCVE (CVE): GCVE-0-2020-8936
GCVE (VulDB): GCVE-100-166412

Entryinfo

Created: 12/16/2020 10:11
Updated: 12/18/2020 23:03
Changes: 12/16/2020 10:11 (38), 12/16/2020 11:08 (2), 12/18/2020 22:56 (3), 12/18/2020 23:03 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!