Lucene search
+L

1043 matches found

ATTACKERKB
ATTACKERKB
added 2023/03/01 8:15 a.m.5 views

CVE-2022-38737

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none...

5.8AI score
SaveExploits0References1
ATTACKERKB
ATTACKERKB
added 2023/03/01 8:15 a.m.6 views

CVE-2022-38735

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none...

5.8AI score
SaveExploits0References1
ATTACKERKB
ATTACKERKB
added 2023/03/01 8:15 a.m.5 views

CVE-2022-38740

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate is unused by its CNA. Notes: none...

5.8AI score
SaveExploits0References1
NVD
NVD
added 2023/02/27 6:15 p.m.13 views

CVE-2018-12195

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues. Notes: none...

6.4AI score
SaveExploits0
ATTACKERKB
ATTACKERKB
added 2023/02/21 11:15 p.m.3 views

CVE-2021-23944

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues. Notes: none...

5.8AI score
SaveExploits0References1
ATTACKERKB
ATTACKERKB
added 2023/02/21 11:15 p.m.5 views

CVE-2021-23941

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues. Notes: none...

5.8AI score
SaveExploits0References1
SUSE CVE
SUSE CVE
added 2023/02/15 6:18 a.m.3 views

SUSE CVE-2005-0751

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate has been revoked by its Candidate Numbering Authority CNA because it was initially assigned to a problem that was not a security issue. Notes: none...

6.9AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 6:17 a.m.5 views

SUSE CVE-2005-2355

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2005-2335, CVE-2005-2356. Reason: due to a typo in an advisory, this candidate was accidentally referenced. Notes: All CVE users should consult CVE-2005-2335 and CVE-2005-2356 to determine the appropriate identifier for the issue...

7.1AI score
SaveExploits1References3
SUSE CVE
SUSE CVE
added 2023/02/15 6:17 a.m.4 views

SUSE CVE-2005-2965

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2005-4802, CVE-2005-4803. Reason: this candidate was intended for one issue, but the description and references inadvertently combined multiple issues. Notes: All CVE users should consult CVE-2005-4802 and CVE-2005-4803 to determine which ID is...

7AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 6:17 a.m.7 views

SUSE CVE-2005-3122

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2005-3424, CVE-2005-3425. Reason: this candidate was intended for one issue, but two different authoritative sources used it for two distinct issues. Notes: All CVE users should consult CVE-2005-3424 and CVE-2005-3425 to determine which ID is...

7AI score
SaveExploits0References7
SUSE CVE
SUSE CVE
added 2023/02/15 6:12 a.m.7 views

SUSE CVE-2007-1356

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...

6.9AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 6:8 a.m.2 views

SUSE CVE-2008-1879

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none...

7AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 6:4 a.m.4 views

SUSE CVE-2009-0795

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2009-0796, CVE-2009-1265. Reason: this candidate was intended for one issue, but a typo caused it to be associated with a different issue. Notes: All CVE users should consult CVE-2009-0796 and CVE-2009-1265 to determine which ID is appropriate. Al...

7AI score
SaveExploits2References3
SUSE CVE
SUSE CVE
added 2023/02/15 6:0 a.m.6 views

SUSE CVE-2010-1144

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2010-0751, CVE-2010-1277. Reason: this candidate was intended for one issue, but it was accidentally assigned to two different issues, one for libnids and another for Zabbix. Notes: All CVE users should consult CVE-2010-0751 libnids and...

7AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 5:55 a.m.3 views

SUSE CVE-2011-0023

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none...

7AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 5:49 a.m.2 views

SUSE CVE-2011-4388

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 2011. Notes: none...

7AI score
SaveExploits0References6
SUSE CVE
SUSE CVE
added 2023/02/15 5:45 a.m.2 views

SUSE CVE-2012-3878

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...

6.9AI score
SaveExploits0References3
SUSE CVE
SUSE CVE
added 2023/02/15 5:43 a.m.4 views

SUSE CVE-2012-5664

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2012-6496, CVE-2012-6497. Reason: this candidate was intended for one issue, but the candidate was publicly used to label concerns about multiple products. Notes: All CVE users should consult CVE-2012-6496 and CVE-2012-6497 to determine which ID i...

7.6AI score
SaveExploits2References9
SUSE CVE
SUSE CVE
added 2023/02/15 5:42 a.m.4 views

SUSE CVE-2013-0188

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2013-0189, CVE-2013-0191. Reason: this identifier was intended for one issue, but it was inadvertently associated with multiple issues. Notes: All CVE users should consult CVE-2013-0189 and CVE-2013-0191 to determine which ID is appropriate. All...

7.3AI score
SaveExploits1References8
SUSE CVE
SUSE CVE
added 2023/02/15 5:42 a.m.5 views

SUSE CVE-2013-0341

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...

6.9AI score
SaveExploits0References3
Rows per page
Query Builder