| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Adobe Acrobat Reader up to 2015.006.30510/2017.011.30158/2020.006.20034. Impacted is an unknown function of the component DLL Handler. The manipulation leads to untrusted search path. This vulnerability is listed as CVE-2020-3803. The attack must be carried out locally. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in Adobe Acrobat Reader up to 2015.006.30510/2017.011.30158/2020.006.20034 (Document Reader Software). It has been rated as critical. This issue affects some unknown processing of the component DLL Handler. The manipulation with an unknown input leads to a untrusted search path vulnerability. Using CWE to declare the problem leads to CWE-426. The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Adobe Acrobat and Reader versions 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier have an insecure library loading (dll hijacking) vulnerability. Successful exploitation could lead to privilege escalation.
The weakness was presented 03/17/2020 as APSB20-13 as confirmed security bulletin (Website). The advisory is shared at helpx.adobe.com. The identification of this vulnerability is CVE-2020-3803 since 12/17/2019. An attack has to be approached locally. Required for exploitation is a simple authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1574 for this issue.
Upgrading to version 2015.006.30518, 2017.011.30166 or 2020.006.20042 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
See VDB-152324, VDB-152325, VDB-152327 and VDB-152328 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.adobe.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Untrusted search pathCWE: CWE-426
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Acrobat Reader 2015.006.30518/2017.011.30166/2020.006.20042
Timeline
12/17/2019 🔍03/17/2020 🔍
03/17/2020 🔍
03/26/2020 🔍
10/05/2020 🔍
Sources
Vendor: adobe.comAdvisory: APSB20-13
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2020-3803 (🔍)
GCVE (CVE): GCVE-0-2020-3803
GCVE (VulDB): GCVE-100-152333
See also: 🔍
Entry
Created: 03/26/2020 07:56Updated: 10/05/2020 07:33
Changes: 03/26/2020 07:56 (44), 03/26/2020 08:01 (18), 10/05/2020 07:33 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.

No comments yet. Languages: en.
Please log in to comment.