|
1 | 1 | { |
2 | 2 | "currentNews": [ |
| 3 | + { |
| 4 | + "id": 452, |
| 5 | + "displayOnHomepageOrder": 1, |
| 6 | + "newsType": "blog", |
| 7 | + "title": "“CVE List Keyword Search” Now Available on CVE.ORG Website", |
| 8 | + "urlKeywords": "CVE List Keyword Search Now Available", |
| 9 | + "date": "2024-12-11", |
| 10 | + "author": { |
| 11 | + "name": "CVE Program", |
| 12 | + "organization": { |
| 13 | + "name": "CVE Program", |
| 14 | + "url": "" |
| 15 | + }, |
| 16 | + "title": "", |
| 17 | + "bio": "" |
| 18 | + }, |
| 19 | + "description": [ |
| 20 | + { |
| 21 | + "contentnewsType": "paragraph", |
| 22 | + "content": "The ability to search <a href='/ResourcesSupport/Glossary?activeTerm=glossaryRecord'>CVE Records</a> by keyword is now available on <a href='/'>CVE.ORG</a>. Keywords may include a <a href='/ResourcesSupport/Glossary?activeTerm=glossaryCVEID'>CVE ID</a> (e.g., CVE-2024-1234), or one or more keywords separated by a space (e.g., authorization, SQL Injection, cross site scripting, etc.)." |
| 23 | + }, |
| 24 | + { |
| 25 | + "contentnewsType": "paragraph", |
| 26 | + "content": "The new <a href='/'>CVE List Keyword Search</a> box—shown below—is located at the top of every page of the website. Please try the new CVE List keyword search and provide your feedback <a href='https://forms.office.com/g/qmmTaYnr5y' target='_blank'>here</a>." |
| 27 | + }, |
| 28 | + { |
| 29 | + "contentnewsType": "image", |
| 30 | + "imageWidth": "", |
| 31 | + "href": "/news/CVEListSearchBox.png", |
| 32 | + "altText": "CVE List Keyword Search box", |
| 33 | + "captionText": "<a href='https://www.cve.org/' target='_blank'>CVE List Keyword Search box</a>" |
| 34 | + }, |
| 35 | + { |
| 36 | + "contentnewsType": "paragraph", |
| 37 | + "content": "Please note that this search is for the CVE List only. It will only search CVE Records. To search the overall website, use the “Site Search” located to the right of the CVE List search box." |
| 38 | + }, |
| 39 | + { |
| 40 | + "contentnewsType": "paragraph", |
| 41 | + "content": "<h3>Continuous Improvement</h3>" |
| 42 | + }, |
| 43 | + { |
| 44 | + "contentnewsType": "paragraph", |
| 45 | + "content": "While Phase 1 brought CVE ID lookup to the new CVE.ORG website, Phase 2 of our search deployment brings keyword searching of the CVE List." |
| 46 | + }, |
| 47 | + { |
| 48 | + "contentnewsType": "paragraph", |
| 49 | + "content": "Users can now search by keywords with letters or numbers (e.g., vendor name, product name and version, vulnerability type, etc.), or by a CVE ID that must include all letters, numbers, and hyphens associated with the CVE ID, (e.g., CVE-2024-12345). Future phases will include adding the ability to search by special characters (e.g., dot (.), forward slash (/), etc. ), and other enhancements suggested by the community." |
| 50 | + }, |
| 51 | + { |
| 52 | + "contentnewsType": "paragraph", |
| 53 | + "content": "Community input is integral for our ability to continuously improve the search capability, so please provide your valuable feedback <a href='https://forms.office.com/g/qmmTaYnr5y' target='_blank'>here</a>." |
| 54 | + }, |
| 55 | + { |
| 56 | + "contentnewsType": "paragraph", |
| 57 | + "content": "It is important to note that the new keyword search capability may be temporarily unavailable when enhancements are added. During these times, the <a href='https://cve.mitre.org/cve/search_cve_list.html' target='_blank'>CVE List legacy search</a> on CVE.MITRE.ORG will remain available for use as a fallback." |
| 58 | + }, |
| 59 | + { |
| 60 | + "contentnewsType": "paragraph", |
| 61 | + "content": "<h3>Search Tips</h3>" |
| 62 | + }, |
| 63 | + { |
| 64 | + "contentnewsType": "paragraph", |
| 65 | + "content": "Enter keywords in the new keyword search box following the guidelines provided below." |
| 66 | + }, |
| 67 | + { |
| 68 | + "contentnewsType": "paragraph", |
| 69 | + "content": "<h4>By CVE ID:</h4>" |
| 70 | + }, |
| 71 | + { |
| 72 | + "contentnewsType": "paragraph", |
| 73 | + "content": "<ul><li>Must include only one CVE ID per search.</li><li>CVE ID must include all letters, numbers, and hyphens associated with the CVE ID, e.g., CVE-2024-12345678.</li><li>“CVE” may be entered as “cve”, “CVE”, or as a combination of uppercase and lowercase, as casing is ignored during search.</li></ul>" |
| 74 | + }, |
| 75 | + { |
| 76 | + "contentnewsType": "paragraph", |
| 77 | + "content": "<h4>By Other Keyword(s):</h4>" |
| 78 | + }, |
| 79 | + { |
| 80 | + "contentnewsType": "paragraph", |
| 81 | + "content": "<ul><li>Must contain only alphanumeric characters, e.g., letters or numbers.</li><li>May contain one or more keywords, separated by a space.</li><li>Keywords may be entered in lowercase, uppercase, or a combination of both. Casing is ignored during search, e.g., the following variations are treated the same and would return the same results: Vulnerabilities, vulnerabilities, VULNERABILITIES.</li></ul>" |
| 82 | + }, |
| 83 | + { |
| 84 | + "contentnewsType": "paragraph", |
| 85 | + "content": "<strong>Note:</strong> Newly published CVE Records are generally available to search within 30 minutes of publication." |
| 86 | + }, |
| 87 | + { |
| 88 | + "contentnewsType": "paragraph", |
| 89 | + "content": "<h3>Requesting Feedback</h3>" |
| 90 | + }, |
| 91 | + { |
| 92 | + "contentnewsType": "paragraph", |
| 93 | + "content": "Thank you in advance for using the “CVE List Keyword Search” and providing your feedback, which will help us improve the capability for the community over time. The feedback form is available <a href='https://forms.office.com/g/qmmTaYnr5y' target='_blank'>here</a>." |
| 94 | + } |
| 95 | + ] |
| 96 | + }, |
3 | 97 | { |
4 | 98 | "id": 451, |
5 | 99 | "newsType": "news", |
|
780 | 874 | }, |
781 | 875 | { |
782 | 876 | "id": 429, |
783 | | - "displayOnHomepageOrder": 1, |
784 | 877 | "newsType": "blog", |
785 | 878 | "title": "CVE Program Celebrates 25 Years of Impact!", |
786 | 879 | "urlKeywords": "CVE Program Celebrates 25 Years", |
|
0 commit comments