7.8
CVE-2024-9250
- EPSS 0.11%
- Veröffentlicht 22.11.2024 22:15:21
- Zuletzt bearbeitet 29.11.2024 18:19:42
- Quelle zdi-disclosures@trendmicro.com
- Teams Watchlist Login
- Unerledigt 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-24489.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Foxit ≫ Pdf Editor SwPlatformwindows Version <= 11.2.10.53951
Foxit ≫ Pdf Editor SwPlatformwindows Version >= 12.0 <= 12.1.7.15526
Foxit ≫ Pdf Editor SwPlatformwindows Version >= 13.0 <= 13.1.3.22478
Foxit ≫ Pdf Editor SwPlatformwindows Version >= 2023.0 <= 2023.3.0.23028
Foxit ≫ Pdf Editor SwPlatformwindows Version >= 2024.0 <= 2024.2.3.25184
Foxit ≫ Pdf Reader SwPlatformwindows Version <= 2024.2.3.25184
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.11% | 0.306 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
|
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.