cve-validation

To validate a CVE identifier against Red Hat Lightspeed, you provide the CVE ID so the system can check its format, retrieve metadata including severity, and assess automated remediation availability before proceeding with planning.

The CVE validation process retrieves metadata from Red Hat Lightspeed, including the vulnerability's severity assessment, remediation status, and whether an automated playbook is available for remediation.

Yes, you can check if an automated remediation playbook exists for a CVE by validating it against Red Hat Lightspeed, which assesses remediation availability and integrates with the remediator for end-to-end playbook generation.

Yes, CVE format validation requires using the get_cve MCP tool with include_details and validate_format parameters, and it performs prerequisite validation with the mcp-lightspeed-validator to ensure identifiers are proper.

You need to validate CVEs in a remediation workflow before proceeding with remediation work, ensuring identifiers are properly formatted, their existence is verified, and severity is assessed to confirm automated remediation options are known.

CVSS scoring and vulnerability logic checks use criteria from consulting vulnerability-logic and cvss-scoring documentation, ensuring proper severity assessment and validation during the CVE format checking and metadata retrieval process.