CVE-2022-20424
Unknown
Last modified
This CVE is reserved or rejected; no details have been published by NVD.
Description
Rejected reason: 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: none.
Timeline
- Published
- Last Modified
- Status
- Rejected
Related CVEs from 2022
- CVE-2022-20419In setOptions of ActivityRecord.java, there is a possible lo…7.8
- CVE-2022-2042Use After Free in GitHub repository vim/vim prior to 8.2.7.8
- CVE-2022-20420In getBackgroundRestrictionExemptionReason of AppRestriction…7.8
- CVE-2022-20421In binder_inc_ref_for_node of binder.c, there is a possible …7.8
- CVE-2022-20422In emulation_proc_handler of armv8_deprecated.c, there is a …7
- CVE-2022-20423In rndis_set_response of rndis.c, there is a possible out of…4.6
- CVE-2022-20425In addAutomaticZenRule of ZenModeHelper.java, there is a pos…5.5
- CVE-2022-20426In multiple functions of many files, there is a possible obs…5.5
- CVE-2022-20427In (TBD) of (TBD), there is a possible way to corrupt memory…6.7
- CVE-2022-20428In (TBD) of (TBD), there is a possible out of bounds write d…6.7
- CVE-2022-20429In CarSettings of app packages, there is a possible permissi…8.8
- CVE-2022-2043MOXA NPort 5110: Firmware Versions 2.10 is vulnerable to an …7.5
Are you affected by CVE-2022-20424?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
