Overview 13,010 matches · 0 in Waratek scope · 0 protected · 3 exploited · 0 CISA KEV · 119 public PoC · 0 EPSS ≥ 0.5
13,010matches
0in Waratek scope0.0%
0protected0.0%
3exploited0.0%
0CISA KEV0.0%
119public PoC0.9%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
0
0.0%
Withdrawn CVE
13,010
100.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
13,010
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 3,471 / year
19921
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19930
19941
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19950
19961
Withdrawn CVE1
Unknown1
not blocked1
Working exploit published1
19971
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
19981
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
199929
Withdrawn CVE29
Unknown29
not blocked29
Working exploit published1
No public exploit28
20001
Withdrawn CVE1
Unknown1
not blocked1
No public exploit1
20013
Withdrawn CVE3
Unknown3
not blocked3
No public exploit3
200214
Withdrawn CVE14
Unknown14
not blocked14
Working exploit published2
No public exploit12
200321
Withdrawn CVE21
Unknown21
not blocked21
Working exploit published1
No public exploit20
200428
Withdrawn CVE28
Unknown28
not blocked28
No public exploit28
200578
Withdrawn CVE78
Unknown78
not blocked78
Working exploit published5
No public exploit73
200651
Withdrawn CVE51
Unknown51
not blocked51
Working exploit published3
No public exploit48
200780
Withdrawn CVE80
Unknown80
not blocked80
Working exploit published3
No public exploit77
200832
Withdrawn CVE32
Unknown32
not blocked32
Working exploit published5
No public exploit27
200946
Withdrawn CVE46
Unknown46
not blocked46
Working exploit published6
No public exploit40
201028
Withdrawn CVE28
Unknown28
not blocked28
Working exploit published2
No public exploit26
201122
Withdrawn CVE22
Unknown22
not blocked22
Working exploit published3
No public exploit19
201263
Withdrawn CVE63
Unknown63
not blocked63
Working exploit published5
No public exploit58
2013137
Withdrawn CVE137
Unknown137
not blocked137
Working exploit published20
No public exploit117
201480
Withdrawn CVE80
Unknown80
not blocked80
Working exploit published11
No public exploit69
2015101
Withdrawn CVE101
Unknown101
not blocked101
Working exploit published5
No public exploit96
201668
Withdrawn CVE68
Unknown68
not blocked68
Working exploit published4
No public exploit64
20173,471
Withdrawn CVE3,471
Unknown3,471
not blocked3,471
Exploited1
Working exploit published10
No public exploit3,460
20181,644
Withdrawn CVE1,644
Unknown1,644
not blocked1,644
Working exploit published5
Proof of concept only1
No public exploit1,638
20191,633
Withdrawn CVE1,633
Unknown1,633
not blocked1,633
Exploited1
Working exploit published3
No public exploit1,629
2020900
Withdrawn CVE900
Unknown900
not blocked900
Working exploit published5
No public exploit895
20211,801
Withdrawn CVE1,801
Unknown1,801
not blocked1,801
Working exploit published1
No public exploit1,800
20221,358
Withdrawn CVE1,358
Unknown1,358
not blocked1,358
Working exploit published4
Proof of concept only6
No public exploit1,348
20231,316
Withdrawn CVE1,316
Unknown1,316
not blocked1,316
Exploited1
Working exploit published6
Proof of concept only1
No public exploit1,308
19931996199920022005200820112014201720202023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-40214 | Unknown | 2023-08-31 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2022. Notes: none. |
| CVE-2023-4609 | Unknown | 2023-08-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-4526 | Unknown | 2023-08-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-4525 | Unknown | 2023-08-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-41269 | Unknown | 2023-08-30 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-4524 | Unknown | 2023-08-25 | Withdrawn CVE | No public exploit | Rejected reason: CVE reject in favor of CVE-2023-40547 |
| CVE-2023-40568 | Unknown | 2023-08-25 | Withdrawn CVE | No public exploit | Rejected reason: GitHub has been informed that the requestor is working with another CNA for these vulnerabilities. |
| CVE-2023-38289 | Unknown | 2023-08-24 | Withdrawn CVE | No public exploit | Rejected reason: Not a Security Issue. |
| CVE-2023-38288 | Unknown | 2023-08-24 | Withdrawn CVE | No public exploit | Rejected reason: Not a Security Issue. |
| CVE-2023-41126 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-41125 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-41124 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-41123 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-41122 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-40270 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-38831. Reason: This candidate is a reservation duplicate of CVE-2023-38831. Notes: All CVE users should reference CVE-2023-38831 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-39583 | Unknown | 2023-08-23 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-38831. Reason: This candidate is a reservation duplicate of CVE-2023-38831. Notes: All CVE users should reference CVE-2023-38831 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-30079 | Unknown | 2023-08-22 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-22652. Reason: This record is a duplicate of CVE-2023-22652. Notes: All CVE users should reference CVE-2023-22652 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. |
| CVE-2023-30078 | Unknown | 2023-08-22 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-32181. Reason: This record is a duplicate of CVE-2023-32181. Notes: All CVE users should reference CVE-2023-32181 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. |
| CVE-2022-40433 | Unknown | 2023-08-22 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** This CVE ID has been rejected by its CNA as it was not a security issue. |
| CVE-2020-20145 | Unknown | 2023-08-22 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2019-14834. Reason: This candidate is a reservation duplicate of CVE-2019-14834. Notes: All CVE users should reference CVE-2019-14834 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2020-19500 | Unknown | 2023-08-22 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2022-4367 | Unknown | 2023-08-21 | Withdrawn CVE | No public exploit | Rejected reason: Duplicate, use CVE-2023-4279 instead. |
| CVE-2023-4413 | Unknown | 2023-08-18 | Withdrawn CVE | No public exploit | 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: Permission to access the file is limited to administrative users only by default. |
| CVE-2023-4330 | Unknown | 2023-08-15 | Withdrawn CVE | No public exploit | Rejected reason: Broadcom were unable to duplicate the attack as described by Intel DCG Team. |
| CVE-2023-39849 | Unknown | 2023-08-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-39848 | Unknown | 2023-08-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2022-3403 | Unknown | 2023-08-11 | Withdrawn CVE | No public exploit | Rejected reason: Duplicate, please use CVE-2023-28931 instead. |
| CVE-2023-4275 | Unknown | 2023-08-10 | Withdrawn CVE | No public exploit | Rejected reason: It is invalid. |
| CVE-2023-4128 | Unknown | 2023-08-10 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-4206, CVE-2023-4207, CVE-2023-4208. Reason: This record is a duplicate of CVE-2023-4206, CVE-2023-4207, CVE-2023-4208. Notes: All CVE users should reference CVE-2023-4206, CVE-2023-4207, CVE-2023-4208 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. |
| CVE-2023-39977 | Unknown | 2023-08-08 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-3268. Reason: This candidate is a reservation duplicate of CVE-2023-3268. Notes: All CVE users should reference CVE-2023-3268 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-38815 | Unknown | 2023-08-08 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-40042. Reason: This candidate is a reservation duplicate of CVE-2023-40042. Notes: All CVE users should reference CVE-2023-40042 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-38814 | Unknown | 2023-08-08 | Withdrawn CVE | No public exploit | 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 in the allowed scope of that CNA's CVE ID assignments. Notes: none. |
| CVE-2023-36546 | Unknown | 2023-08-08 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-2230 | Unknown | 2023-08-08 | Withdrawn CVE | No public exploit | Rejected reason: Accidental Assignment |
| CVE-2023-4205 | Unknown | 2023-08-07 | Withdrawn CVE | No public exploit | Rejected reason: This was deemed as a false positive both by the reporter and upstream kernel. |
| CVE-2023-39552 | Unknown | 2023-08-04 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-0527. Reason: This candidate is a reservation duplicate of CVE-2023-0527. Notes: All CVE users should reference CVE-2023-0527 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-38707 | Unknown | 2023-08-04 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has been rejected because of [CNA rule 7.4.7](https://www.cve.org/ResourcesSupport/AllResources/CNARules#section_7_assignment_rules): ``` 7.4.7 CNAs SHOULD NOT assign CVE IDs to vulnerabilities in products that are not publicly available or licensable. ``` The repository with the vulnerable code is private, and therefore the product is not publicly available. |
| CVE-2023-38696 | Unknown | 2023-08-04 | Withdrawn CVE | No public exploit | Rejected reason: This CVE has been rejected because it is unclear whether the issue rests in the original repository `microsoft/ContosoAir`, the forked repository `Apetree100122/ContosoAir`, or both. If the Microsoft repository is vulnerable, [Microsoft](https://www.cve.org/PartnerInformation/ListofPartners/partner/microsoft) is the appropriate CVE Numbering Authority. |
| CVE-2023-38812 | Unknown | 2023-08-03 | Withdrawn CVE | No public exploit | 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. |
| CVE-2022-42986 | Unknown | 2023-08-03 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-39122. Reason: This candidate is a reservation duplicate of CVE-2023-39122. Notes: All CVE users should reference CVE-2023-39122 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-32302 | Unknown | 2023-08-01 | Withdrawn CVE | No public exploit | Rejected reason: Authoritative user requested CVE rejection https://github.com/github/advisory-database/pull/2575#issuecomment-1745811653 |
| CVE-2023-4026 | Unknown | 2023-07-31 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2023-4024. Reason: This record is a duplicate of CVE-2023-4024. Notes: All CVE users should reference CVE-2023-4024 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage. |
| CVE-2023-4010 | Unknown | 2023-07-31 | Withdrawn CVE | No public exploit | Rejected reason: Rejected because the CVE description attributes a vulnerability to a non-existent Linux kernel function (usb_giveback_urb()) and the reported issue cannot be mapped to any valid codebase. |
| CVE-2023-39190 | Unknown | 2023-07-28 | Withdrawn CVE | No public exploit | Rejected reason: CVE-2023-39190 was found to be a duplicate of CVE-2023-31436. Please see https://access.redhat.com/security/cve/CVE-2023-31436 for information about affected products and security errata. |
| CVE-2023-29845 | Unknown | 2023-07-27 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2023-3451 | Unknown | 2023-07-26 | Withdrawn CVE | No public exploit | Rejected reason: Duplicate CVE. Please use CVE-2023-32297. |
| CVE-2023-32001 | Unknown | 2023-07-26 | Withdrawn CVE | No public exploit | Rejected reason: We issued this CVE pre-maturely, as we have subsequently realized that this issue points out a problem that there really is no safe measures around or protections for. |
| CVE-2023-3870 | Unknown | 2023-07-24 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2023-25180 | Unknown | 2023-07-20 | Withdrawn CVE | No public exploit | Rejected reason: Rejected by upstream. |
| CVE-2023-24593 | Unknown | 2023-07-20 | Withdrawn CVE | No public exploit | Rejected reason: Rejected by upstream. |
| CVE-2023-38326 | Unknown | 2023-07-18 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-36120 | Unknown | 2023-07-18 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2023-37850 | Unknown | 2023-07-17 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-3496 | Unknown | 2023-07-17 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-3418 | Unknown | 2023-07-17 | Withdrawn CVE | No public exploit | Rejected reason: The issue is not in the plugin itself but the underlying chat service |
| CVE-2023-37811 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37810 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37809 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37808 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37807 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37806 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37805 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37804 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37803 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37802 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37801 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-37800 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-36169 | Unknown | 2023-07-15 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-36168 | Unknown | 2023-07-15 | Withdrawn CVE | Proof of concept only | 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. |
| CVE-2023-36166 | Unknown | 2023-07-15 | Withdrawn CVE | Working exploit published | 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. |
| CVE-2023-36165 | Unknown | 2023-07-15 | Withdrawn CVE | Working exploit published | 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. |
| CVE-2023-36119 | Unknown | 2023-07-14 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none. |
| CVE-2023-21261 | Unknown | 2023-07-13 | Withdrawn CVE | No public exploit | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
| CVE-2023-36167 | Unknown | 2023-07-11 | Withdrawn CVE | Working exploit published | 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. |
| CVE-2023-36164 | Unknown | 2023-07-11 | Withdrawn CVE | Working exploit published | 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. |
| CVE-2023-37151 | Unknown | 2023-07-10 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-2246. Reason: This candidate is a reservation duplicate of CVE-2023-2246. Notes: All CVE users should reference CVE-2023-2246 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-36935 | Unknown | 2023-07-10 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-36360 | Unknown | 2023-07-10 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-34682 | Unknown | 2023-07-10 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-33715 | Unknown | 2023-07-07 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-36262 | Unknown | 2023-07-03 | Withdrawn CVE | No public exploit | 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. |
| CVE-2023-35935 | Unknown | 2023-07-03 | Withdrawn CVE | No public exploit | Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-31999. Reason: This candidate is a reservation duplicate of CVE-2023-31999. Notes: All CVE users should reference CVE-2023-31999 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage. |
| CVE-2023-36001 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-35999 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-35700 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-35073 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-34211 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-3370 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-4854 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-43587 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-43586 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-43585 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-43584 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-43583 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-42338 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-42337 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-2570 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2022-22507 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2020-15730 | Unknown | 2023-07-02 | Withdrawn CVE | No public exploit | Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none. |
| CVE-2023-3117 | Unknown | 2023-06-30 | Withdrawn CVE | No public exploit | Rejected reason: Duplicate of CVE-2023-3390. |