|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.
A vulnerability was found in aws-sdk shared-ini-file-loader (version unknown). It has been classified as critical. Affected is some unknown processing of the component INI File Parser. The manipulation with an unknown input leads to a privilege escalation vulnerability. CWE is classifying the issue as CWE-74. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
This affects the package @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9; the package aws-sdk before 2.814.0. If an attacker submits a malicious INI file to an application that parses it with loadSharedConfigFiles , they will pollute the prototype on the application. This can be exploited further depending on the context.
The weakness was published 01/19/2021 as SNYK-JS-AWSSDK-1059424. The advisory is available at snyk.io. This vulnerability is traded as CVE-2020-28472 since 11/12/2020. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.
Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
NVD Base Score: 🔒
ExploitingClass: Privilege escalation
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceThreat: 🔍
0-Day Time: 🔒
Timeline11/12/2020 CVE assigned
01/19/2021 +68 days Advisory disclosed
01/19/2021 +0 days VulDB entry created
02/15/2021 +27 days VulDB last update
CVE: CVE-2020-28472 (🔒)
EntryCreated: 01/19/2021 02:35 PM
Updated: 02/15/2021 10:06 AM
Changes: (19) vulnerability_cvss3_nvd_av vulnerability_cvss3_nvd_ac vulnerability_cvss3_nvd_pr vulnerability_cvss3_nvd_ui vulnerability_cvss3_nvd_s vulnerability_cvss3_nvd_c vulnerability_cvss3_nvd_i vulnerability_cvss3_nvd_a vulnerability_cvss2_nvd_av vulnerability_cvss2_nvd_ac vulnerability_cvss2_nvd_au vulnerability_cvss2_nvd_ci vulnerability_cvss2_nvd_ii vulnerability_cvss2_nvd_ai source_cve_cna vulnerability_cvss3_meta_basescore vulnerability_cvss3_meta_tempscore vulnerability_cvss2_nvd_basescore vulnerability_cvss3_nvd_basescore
Do you want to use VulDB in your project?
Use the official API to access entries easily!