Skip to content

Commit 0ab5707

Browse files
authored
#3676 Updates for CVE List Search v1.2 (#3680)
1 parent 26ec75e commit 0ab5707

File tree

3 files changed

+27
-20
lines changed

3 files changed

+27
-20
lines changed

src/assets/data/NotificationBanner.json

Lines changed: 1 addition & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -22,29 +22,12 @@
2222
},
2323
{
2424
"contentType": "internalLink",
25-
"link": "/Media/News/item/blog/2025/06/11/CVE-List-Keyword-Search-Updated",
25+
"link": "/ResourcesSupport/FAQs#pc_cve_list_basicssearch_cve",
2626
"linkText": "here"
2727
},
2828
{
2929
"contentType": "paragraph",
3030
"content": "."
31-
},
32-
{
33-
"contentType": "paragraph",
34-
"content": "<br/><br/>"
35-
},
36-
{
37-
"contentType": "paragraph",
38-
"content": "<b>NOTICE &mdash;</b>"
39-
},
40-
{
41-
"contentType": "internalLink",
42-
"link": "/",
43-
"linkText": "CVE List Search"
44-
},
45-
{
46-
"contentType": "paragraph",
47-
"content": "on this CVE.ORG website will be <strong>unavailable on August 27, 2025, between 1:00 PM and 4:00 PM EDT</strong> so that the capability can be upgraded. As a result, searching CVE IDs and CVE Records will be unavailable during this time. We apologize for the inconvenience and thank you for your understanding."
4831
}
4932
]
5033
}

src/assets/data/faqs.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -271,7 +271,7 @@
271271
"questionId": "search_cve",
272272
"questionText": "How do I search the CVE List",
273273
"questionResponseParagraphs": [
274-
"You may search using:<br/><ul><li><strong>IDs</strong><ul><li>CVE ID<ul><li>Specific <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE ID</a> (e.g., “CVE-2015-8405”)</li><li>Note that this returns records where there is a match for the CVE ID anywhere in the CVE Record (e.g., “CVE-2015-8405” returns the CVE named, as well as any CVEs that have that CVE ID in other fields, such as in the description)</li><li>The nominal CVE ID Year (e.g., “CVE-2025” returns all CVEs reserved in the CVE-2025 year series)</li><li>The year must be a full year (e.g., “CVE-202” is invalid and will produce no results)</li></ul></li><li>CWE ID<ul><li>Specific <a href='/About/RelatedEfforts#CWE'>Common Weakness Enumeration (CWE&trade;)</a> entries (e.g., “CWE-123”)</li></ul></li><li> CAPEC ID<ul><li>Specific <a href='/About/RelatedEfforts#CAPEC'>Common Attack Pattern Enumerations and Classification (CAPEC&trade;)</a> entries (e.g., “CAPEC-123”)</li></ul></li></ul></li><li><strong>General</strong><ul><li>Note that if you provide multiple CVE IDs, the search will only return results that contain ALL CVE IDs you specify in each record, which may not be what you expect</li><li>Search terms are case-insensitive and may contain words of alphanumeric and Unicode characters</li><li>Supported search scenarios include:<ul><li>Hyphenated words (e.g., “man-in-the-middle”)</li><li>Exact version strings (e.g., “6.17.4”)<li>Exact IPv4 strings (e.g., “127.0.0.1”)</li><li>Exact filenames (e.g., “main.cpp”)</li><li>URLs (e.g., “http://www.ibm.com/support/docview.wss?uid”)</li></ul></li><li>Symbols currently not supported are:\u00a0\u00a0\u00a0() {} [] \" ' ` &lt;&gt; | ; ! ~ ^ * + %</li></ul></li></ul>"
274+
"You may search using:<br/><ul><li><strong>IDs</strong><ul><li>CVE ID<ul><li>Specific <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE ID</a> (e.g., “CVE-2015-8405”)</li><li>Note that this returns records where there is a match for the CVE ID anywhere in the CVE Record (e.g., “CVE-2015-8405” returns the CVE named, as well as any CVEs that have that CVE ID in other fields, such as in the description)</li><li>The nominal CVE ID Year (e.g., “CVE-2025” returns all CVEs reserved in the CVE-2025 year series)</li><li>The year must be a full year (e.g., “CVE-202” is invalid and will produce no results)</li></ul></li><li>CWE ID<ul><li>Specific <a href='/About/RelatedEfforts#CWE'>Common Weakness Enumeration (CWE&trade;)</a> entries (e.g., “CWE-123”)</li></ul></li><li> CAPEC ID<ul><li>Specific <a href='/About/RelatedEfforts#CAPEC'>Common Attack Pattern Enumerations and Classification (CAPEC&trade;)</a> entries (e.g., “CAPEC-123”)</li></ul></li></ul></li><li><strong>General</strong><ul><li>Note that if you provide multiple CVE IDs, the search will only return results that contain ALL CVE IDs you specify in each record, which may not be what you expect</li><li>Search terms are case-insensitive and may contain words of alphanumeric and Unicode characters</li><li>The wildcard characters “*” and “?” are now supported, which allows searching for patterns instead of only exact matches. For example, searching for “vuln*” would return any CVE Records that contains the word “vulnerable” or “vulnerability”, as well as any other word that starts with “vuln”. The “?” is similar but matches only a single character, useful for finding slight variations in how a word is spelled. Including the “?” will match any letter, number, or symbol in the position in which it is placed. For example, searching for “reject??” would return any CVE Records that include “reject” followed by any other two characters (i.e., letters, numbers, or symbols) such as “rejected”, “rejector”, “reject61”, etc.</li><li>Supported search scenarios include:<br/><ul><li>Wildcards (e.g., “vuln*”, “reject??”)</li><li>Hyphenated words (e.g., “man-in-the-middle”)</li><li>Exact version strings (e.g., “6.17.4”)<li>Exact IPv4 strings (e.g., “127.0.0.1”)</li><li>Exact filenames (e.g., “main.cpp”)</li><li>URLs (e.g., “http://www.ibm.com/support/docview.wss?uid”)</li></ul></li><li>Symbols currently not supported are:\u00a0\u00a0\u00a0() {} [] \" ' ` &lt;&gt; | ; ! ~ ^ + %</li></ul></li></ul>"
275275
]
276276
},
277277
{

src/assets/data/news.json

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,30 @@
11
{
22
"currentNews": [
3+
{
4+
"id": 566,
5+
"newsType": "news",
6+
"title": "Searching for Patterns Now Available in “CVE List Keyword Search” on CVE.ORG Website",
7+
"urlKeywords": "CVE List Keyword Search Updated CVE ORG",
8+
"date": "2025-08-27",
9+
"description": [
10+
{
11+
"contentnewsType": "paragraph",
12+
"content": "“<a href='/'>CVE List Keyword Search</a>” on the CVE.ORG has been updated based upon feedback back from users. As a reminder, this search is for the CVE List only. It will only search <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a>. To search the overall website, use the “Site Search” located to the right of the CVE List search box above."
13+
},
14+
{
15+
"contentnewsType": "paragraph",
16+
"content": "This update to the CVE List Keyword Search adds support for wildcard character search scenarios “*” and “?”, which enable searching for patterns instead of only exact matches. For example, searching for “vuln*” would return any CVE Records that contains the word “vulnerable” or “vulnerability”, as well as any other word that starts with “vuln”. The “?” is similar but matches only a single character, useful for finding slight variations in how a word is spelled. Including the “?” will match any letter, number, or symbol in the position in which it is placed. For example, searching for “reject??” would return any CVE Records that include “reject” followed by any other two characters (i.e., letters, numbers, or symbols) such as “rejected”, “rejector”, “reject61”, etc."
17+
},
18+
{
19+
"contentnewsType": "paragraph",
20+
"content": "View the complete list of CVE List keyword search tips <a href='/ResourcesSupport/FAQs#pc_cve_list_basicssearch_cve'>here</a>."
21+
},
22+
{
23+
"contentnewsType": "paragraph",
24+
"content": "We thank everyone who provided feedback, which continues to help us improve the capability for the community over time."
25+
}
26+
]
27+
},
328
{
429
"id": 565,
530
"newsType": "news",
@@ -65,7 +90,6 @@
6590
},
6691
{
6792
"id": 562,
68-
"displayOnHomepageOrder": 0,
6993
"newsType": "news",
7094
"title": "All Links from Legacy “cve.mitre.org” Website Now Redirect to CVE.ORG",
7195
"urlKeywords": "cve mitre org Redirects to CVE ORG",

0 commit comments

Comments
 (0)