CVE-2025-2724
Unknown
Last modified
This CVE is reserved or rejected; no details have been published by NVD.
Description
Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The code maintainer explains that "the only way to get an object of type GsfMSOleSortingKey is via gsf_msole_sorting_key_new which adds that extra zero element".
Timeline
- Published
- Last Modified
- Status
- Rejected
Related CVEs from 2025
- CVE-2025-27232An authenticated Zabbix Super Admin can exploit the oauth.au…4.9
- CVE-2025-27233Zabbix Agent 2 smartctl plugin does not properly sanitize sm…5.7
- CVE-2025-27234Zabbix Agent 2 smartctl plugin does not properly sanitize sm…7.3
- CVE-2025-27236A regular Zabbix user can search other users in their user g…6.5
- CVE-2025-27237In Zabbix Agent and Agent 2 on Windows, the OpenSSL configur…7.3
- CVE-2025-27238Due to a bug in Zabbix API, the hostprototype.get method lis…3.5
- CVE-2025-27240A Zabbix adminitrator can inject arbitrary SQL during the au…7.2
- CVE-2025-27241in OpenHarmony v5.0.3 and prior versions allow a local attac…5.5
- CVE-2025-27242in OpenHarmony v5.0.3 and prior versions allow a local attac…5.5
- CVE-2025-27243Out-of-bounds write in the firmware for some Intel(R) Ethern…4.4
- CVE-2025-27244AssetView and AssetView CLOUD contain an issue with acquirin…5.9
- CVE-2025-27245Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2025-2724?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
