Search for Common Vulnerabilities and Exposures (CVE) by ID. View CVSS scores, descriptions, and affected products.
Start with a complete identifier such as CVE-2021-44228. The viewer uses that identifier to locate the corresponding CVE record and presents the available description, CVSS information, and affected-product data. It answers questions about one already identified vulnerability; it does not discover vulnerabilities from a product name or scan a device. The common mistake is treating an affected-product entry as proof that a particular installation is vulnerable. Version, configuration, platform, and vendor guidance still need to be checked.
Enter the identifier assigned by the CVE Program, including the CVE prefix, four-digit year, and sequence number. The identifier is the lookup key for a single record. A syntactically plausible identifier may still have no public details because it is reserved, rejected, not yet available to the viewer, or simply does not exist.
The result groups the record's available description, CVSS score or vector, and affected-product information. A CVSS base score summarizes severity from defined metric values; it is not a probability that exploitation will occur. Product entries identify the scope described by the record, but names and version boundaries may not match the labels used in local software inventories.
No. This viewer is intended for lookup by a known CVE identifier. If you only know the vendor, product, or vulnerability description, first use a vulnerability catalog or the vendor's security-advisory search to identify candidate CVE IDs. Then look up each identifier here to inspect its individual record.
No. CVSS describes the technical severity represented by its metric values, not your asset's exposure or business priority. Confirm that the affected product and version match, then consider configuration, network reachability, compensating controls, exploitation evidence, asset importance, and vendor remediation guidance before choosing a response deadline.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.