CVE-2022-2331
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 is unused by its CNA. Notes: none.
Timeline
- Published
- Last Modified
- Status
- Rejected
Related CVEs from 2022
- CVE-2022-23302JMSSink in all versions of Log4j 1.x is vulnerable to deseri…8.8
- CVE-2022-23303The implementations of SAE in hostapd before 2.10 and wpa_su…9.8
- CVE-2022-23304The implementations of EAP-pwd in hostapd before 2.10 and wp…9.8
- CVE-2022-23305By design, the JDBCAppender in Log4j 1.2.x accepts an SQL st…9.8
- CVE-2022-23307CVE-2020-9493 identified a deserialization issue that was pr…8.8
- CVE-2022-23308valid.c in libxml2 before 2.9.13 has a use-after-free of ID …7.5
- CVE-2022-23312A vulnerability has been identified in Spectrum Power 4 (All…6.1
- CVE-2022-23314MCMS v5.2.4 was discovered to contain a SQL injection vulner…9.8
- CVE-2022-23315MCMS v5.2.4 was discovered to contain an arbitrary file uplo…9.8
- CVE-2022-23316An issue was discovered in taoCMS v3.0.2. There is an arbitr…4.9
- CVE-2022-23317CobaltStrike <=4.5 HTTP(S) listener does not determine wheth…7.5
- CVE-2022-23318A heap-buffer-overflow in pcf2bdf, versions >= 1.05 allows a…7.1
Are you affected by CVE-2022-2331?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
