> For the complete documentation index, see [llms.txt](https://helm.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://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/prioritize-vulnerabilities/manage-vulnerabilities/view-vulnerability-details.md). # View vulnerability details Depending on your organization, you’ll likely want to start with the most critical vulnerabilities first, so that you can assess their severity given your particular device, its environment and its use. In the **Base score** column, you’ll see both a v2 and a v3 score. Older devices may not have a v3 score, while newer devices may not have a v2 score. We recommend that you mitigate the v3 score first. ## Rescore a vulnerability You can individually rescore any vulnerability associated with a particular product version. If you've already [applied a rescore profile](/~/changes/KjixZskptrAaNWiTYnvj/rescore-vulnerabilities/rescore-all-vulnerabilities-for-a-product-version.md) to this product version, this individual rescore will override the profile rescore. Refer to [Rescore an individual vulnerability](/~/changes/KjixZskptrAaNWiTYnvj/rescore-vulnerabilities/rescore-an-individual-vulnerability.md) for more information. ## Remediate a vulnerability Initially, all of your vulnerabilities will have a **Status** of **blank**. For CycloneDX status, you'll ultimately want to remediate each of these to either **Exploitable** or **Not affected**. For VEX status, you’ll ultimately want to remediate each of these to either **Affected** or **Not affected**. Refer to [Rescore an individual vulnerability](/~/changes/KjixZskptrAaNWiTYnvj/remediate-vulnerabilities/remediate-a-vulnerability.md) for more information. Depending on your organization, you’ll likely want to start with the most critical vulnerabilities first, so that you can assess their severity given your particular device, its environment and its use. In the **Base score** column, you’ll see both a v2 and a v3 score. Older devices may not have a v3 score, while newer devices may not have a v2 score. We recommend that you mitigate the v3 score first. {% hint style="info" %} If you’ve previously assessed a vulnerability, but you see an **Updated on date** display in the **Detected on** column, this indicates that the vulnerability has been updated. You’ll want to check to make sure that this doesn’t increase its severity or exploitability for your particular case. {% endhint %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helm.docs.medcrypt.com/~/changes/KjixZskptrAaNWiTYnvj/prioritize-vulnerabilities/manage-vulnerabilities/view-vulnerability-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.