8.8
CVE-2024-25648
- EPSS 2.17%
- Published 30.04.2024 15:15:52
- Last modified 22.08.2025 14:59:29
- Source talos-cna@cisco.com
- Teams watchlist Login
- Open Login
A use-after-free vulnerability exists in the way Foxit Reader 2024.1.0.23997 handles a ComboBox widget. A specially crafted JavaScript code inside a malicious PDF document can trigger reuse of a previously freed object, which can lead to memory corruption and result in arbitrary code execution. An attacker needs to trick the user into opening the malicious file to trigger this vulnerability. Exploitation is also possible if a user visits a specially crafted, malicious site if the browser plugin extension is enabled.
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.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 Editor Version2024.1.0.23997
Foxit ≫ Pdf Reader Version2024.1.0.23997
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 Editor Version2024.1.0.63682
Foxit ≫ Pdf Reader Version2024.1.0.63682
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 2.17% | 0.837 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
talos-cna@cisco.com | 8.8 | 2.8 | 5.9 |
CVSS:3.1/AV:N/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.