| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Foxit Reader 9.0.1.1049. It has been classified as critical. Affected by this issue is the function addAnnot. This manipulation causes type conversion.
This vulnerability is registered as CVE-2018-14241. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as critical was found in Foxit Reader 9.0.1.1049 (Document Reader Software). Affected by this vulnerability is the function addAnnot. The manipulation with an unknown input leads to a type conversion vulnerability. The CWE definition for the vulnerability is CWE-704. The product does not correctly convert an object, resource, or structure from one type to a different type. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Foxit Reader 9.0.1.1049. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the addAnnot method. By performing actions in JavaScript, an attacker can trigger a type confusion condition. An attacker can leverage this vulnerability to execute code under the context of the current process. Was ZDI-CAN-6004.
The bug was discovered 07/19/2018. The weakness was published 07/31/2018 (Website). The advisory is shared at foxitsoftware.com. This vulnerability is known as CVE-2018-14241 since 07/16/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 12 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-82783, VDB-82784, VDB-82785 and VDB-82786. 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.foxitsoftware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: Type conversionCWE: CWE-704
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/16/2018 🔍07/19/2018 🔍
07/31/2018 🔍
07/31/2018 🔍
08/01/2018 🔍
03/11/2020 🔍
Sources
Vendor: foxitsoftware.comAdvisory: foxitsoftware.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2018-14241 (🔍)
GCVE (CVE): GCVE-0-2018-14241
GCVE (VulDB): GCVE-100-122365
See also: 🔍
Entry
Created: 08/01/2018 07:43Updated: 03/11/2020 15:24
Changes: 08/01/2018 07:43 (61), 03/11/2020 15:24 (2)
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.