8.8

CVE-2024-25648

Exploit

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
Diese Information steht angemeldeten Benutzern zur Verfügung.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
FoxitPdf Editor Version <= 11.2.8.53842
   MicrosoftWindows Version-
FoxitPdf Editor Version >= 12.0.0.12394 <= 12.1.4.15400
   MicrosoftWindows Version-
FoxitPdf Editor Version >= 13.0.0.21632 <= 13.0.1.21693
   MicrosoftWindows Version-
FoxitPdf Editor Version >= 2023.1.0.15510 <= 2023.3.0.23028
   MicrosoftWindows Version-
FoxitPdf Editor Version2024.1.0.23997
   MicrosoftWindows Version-
FoxitPdf Reader Version2024.1.0.23997
   MicrosoftWindows Version-
FoxitPdf Editor Version <= 11.1.6.0109
   ApplemacOS Version-
FoxitPdf Editor Version >= 12.0.0.0601 <= 12.1.2.55366
   ApplemacOS Version-
FoxitPdf Editor Version >= 13.0.0.61829 <= 13.0.1.61866
   ApplemacOS Version-
FoxitPdf Editor Version >= 2023.1.0.55583 <= 2023.3.0.63083
   ApplemacOS Version-
FoxitPdf Editor Version2024.1.0.63682
   ApplemacOS Version-
FoxitPdf Reader Version2024.1.0.63682
   ApplemacOS Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 2.17% 0.837
CVSS Metriken
Quelle 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.