> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/medcrypt-documentation/medisao/search-cves-and-check-impact.md). # Search CVEs and check impact on your devices **CVE Search** lets you search MedISAO's vulnerability database, open the full record for any CVE, and save searches so you get a regular email digest of new matches. A CVE (Common Vulnerabilities and Exposures) entry is the public, numbered record of a known vulnerability, such as CVE-2024-12345. ## Before you begin * Your organization's plan must include MedISAO. ## Search the database 1. In the sidebar, select **CVE Search**. The **Vulnerability Database** page opens and shows the most recent vulnerabilities. 2. Type into the search box (**Search CVEs by description, ID...**) and select **Search**, or press Enter. 3. The count above the results changes to show how many vulnerabilities matched. The results table has these columns: | Column | What it shows | | --------------------------- | ------------------------------------------------------------------------------- | | **CVE ID** | The CVE identifier. Select it to open the CVE detail page. | | **SEVERITY** | The severity rating and CVSS base score. | | **DESCRIPTION** | The start of the CVE description. | | **PUBLISHED** / **UPDATED** | When the CVE was first published and last changed. | | **AI** | An **AI** badge means MedISAO's AI-enhanced analysis is available for this CVE. | CVSS (Common Vulnerability Scoring System) is the standard 0.0 to 10.0 scale for how severe a vulnerability is. ## Write a precise query with Advanced Mode Plain search matches on description and ID. For more control, turn on **Advanced Mode** and write a structured query against specific fields. As you type, a list suggests field names and values. Examples shown in the app: * `description ~ "buffer overflow"` * `description ~ "remote code" and ai_enhanced = True` * `updated > "2024-01-01"` If the query has a syntax error, a **Search Error** message shows these examples again. ### Let AI write the query for you 1. Select the sparkle button (**AI Query Assistant**) next to **Search**. 2. Describe what you want in plain English, for example *"Show me critical SQL injection CVEs from 2024 that have AI analysis"*. 3. Select **Generate Query**. The assistant puts the query in the search box, turns on **Advanced Mode**, and runs the search. Check the generated query before you rely on the results. ## Save a search and get email digests 1. Run a search you want to keep. 2. Select **Save**. 3. Enter a **Filter Name**. 4. If you want new matches sent to you by email, select **Include in weekly email digest**, **Include in monthly email digest**, or both. 5. Select **Save Filter**. To run a saved search again, open **Saved Filters** and select it. To delete one, select the trash icon next to its name. To share saved filters with a colleague or move them between accounts, select **Export** to download them as a JSON file. Your colleague then selects **Import** and chooses that file. ## Read a CVE's detail page Select a **CVE ID** to open its detail page. Select **Back to Search** to return to your results. The detail page includes: * **Header:** The CVE ID, **Published** and **Updated** dates, severity badge, an **AI Enhanced** badge where it applies, and badges for the attack vector and attack complexity. * **CVSS Metrics:** The base score, severity, vector string, and each metric. If the CVE has been scored under more than one CVSS version (for example **CVSS 4.0** and **CVSS 3.1**), use the version selector or the **All CVSS Scores** summary to switch between them. * **Description:** The full CVE description. * **Update Recommendation** and **Mitigation Steps:** AI-generated guidance, marked **AI Insight**, on what to update and how to reduce risk until you can. If the guidance isn't ready yet, the section shows **Generating...** and fills in automatically when it is. * **Affected Products:** The **VENDOR**, **PRODUCT**, and **CPE** for each affected product. A CPE (Common Platform Enumeration) is a standard name for a piece of software or hardware. Comparing CPEs with the components in your devices tells you whether the CVE could affect you. * **References:** Links to advisories, patches, and other sources, each tagged with its source. {% hint style="warning" %} **Update Recommendation** and **Mitigation Steps** are AI-generated. Confirm them against the vendor's own advisory in **References** before you act on them. {% endhint %} ## Check impact on your devices with Ask MSI To find out whether a CVE matters for your devices, ask Ask MSI while the CVE's detail page is open. 1. Open the CVE's detail page. 2. Select the **Ask MSI** button at the bottom of the screen. (If no device is selected, the button may read **Ask across all devices**.) 3. Ask your question, for example *"Does this CVE affect any of my devices?"* or *"What would an attacker need to exploit this on our infusion pump?"* Ask MSI knows which CVE you're looking at, so you don't need to paste the ID or description. ## Next steps * [Search for a product's vulnerabilities](/medcrypt-documentation/medisao/search-for-a-products-vulnerabilities.md): start from a vendor, product, or package instead of a keyword. * [Follow security advisories](/medcrypt-documentation/medisao/follow-security-advisories.md): read curated advisories that put CVEs in context. * [Ask MSI a question](/medcrypt-documentation/msi/get-started/ask-msi.md): learn more about how Ask MSI answers and cites its sources. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.medcrypt.com/medcrypt-documentation/medisao/search-cves-and-check-impact.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.