7.8
CVE-2024-30365
- EPSS 2.22%
- Published 02.04.2024 21:15:50
- Last modified 08.08.2025 18:25:16
- Source zdi-disclosures@trendmicro.com
- Teams watchlist Login
- Open Login
Foxit PDF Reader AcroForm Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader. 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 handling of AcroForms. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-22947.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
This information is available to logged-in users. Login
Data is provided by the National Vulnerability Database (NVD)
Foxit ≫ Pdf Editor Version <= 11.1.6.0109
Foxit ≫ Pdf Editor Version >= 12.0.0.0601 <= 12.1.2.55366
Foxit ≫ Pdf Editor Version >= 13.0.0.61829 <= 13.0.1.61866
Foxit ≫ Pdf Editor Version >= 2023.1.0.55583 <= 2023.3.0.63083
Foxit ≫ Pdf Reader Version <= 2023.3.0.63083
Foxit ≫ Pdf Editor Version <= 10.1.12.37872
Foxit ≫ Pdf Editor Version >= 11.0.0.49893 <= 11.2.8.53842
Foxit ≫ Pdf Editor Version >= 12.0.0.12394 <= 12.1.4.15400
Foxit ≫ Pdf Editor Version >= 13.0.0.21632 <= 13.0.1.21693
Foxit ≫ Pdf Editor Version >= 2023.1.0.15510 <= 2023.3.0.23028
Foxit ≫ Pdf Reader Version <= 2023.3.0.23028
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 2.22% | 0.838 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
zdi-disclosures@trendmicro.com | 7.8 | 1.8 | 5.9 |
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.