CVE - How Vulnerabilities Are Identified and Tracked
About 2 min read
CVE (Common Vulnerabilities and Exposures) is an international naming convention that assigns a unique identifier to publicly disclosed security vulnerabilities. Composed of a year and a sequential number, such as "CVE-2024-12345," it allows the same vulnerability to be referenced accurately across different vendors and tools. The MITRE Corporation began operating it in 1999, and as of 2025 more than 270,000 CVEs have been registered in total.
Identifying the Scope of Impact with an SBOM
When a critical CVE is disclosed, the first challenge is identifying where in your organization the affected product and version are in use. In cases such as CVE-2024-3094, in which a backdoor was planted in xz Utils, the response starts with this identification. If software composition information is maintained day to day as an SBOM (software bill of materials), the affected locations can be found simply by matching against the CVE number; organizations without such an inventory need time for the investigation itself. When no fixed version exists yet, downgrading to an unaffected older version can also be a realistic countermeasure.
The CVE Lifecycle
History and How It Works
Before the CVE system existed, each vendor assigned a different name to the same vulnerability, causing confusion in information sharing. CVE numbers are issued by accredited bodies called CNAs (CVE Numbering Authorities). Major vendors such as Google, Microsoft, and Red Hat hold the authority to independently assign CVE numbers as CNAs for their own products. The severity of a vulnerability is evaluated with a CVSS (Common Vulnerability Scoring System) score from 0.0 to 10.0, and the v3.1 specification classifies scores of 9.0 to 10.0 as "Critical."
Practical Application
In patch management work, the vulnerability in question is identified by its CVE number, and response priorities are then decided. The judgment considers not only the CVSS score but also whether exploit code has actually been published and whether the vulnerability applies to your own environment. CVE information on the NVD (National Vulnerability Database) and JVN (Japan Vulnerability Notes) can be combined with threat intelligence to inform the response.
Was this article helpful?
Related Terms
- Secure Coding Practices for DevelopersSecure coding helps reduce injection, XSS, and buffer overflow flaws at the coding stage. Learn OWASP Top 10 guidelines and input validation techniques for safer apps.
- Rainbow Table Attacks - Cracking Hashed PasswordsRainbow tables map precomputed hashes to plaintext for instant password lookups. See why salted hashes and modern algorithms render this attack obsolete.
- Principle of Least Privilege - Minimize PermissionsLeast privilege grants users only the minimum access they need. Learn how it limits blast radius, prevents insider threats, and supports zero trust.
- Sandboxing - Isolating Untrusted Code SafelyA sandbox runs suspicious programs in an isolated environment to prevent system damage. See how sandboxing is used to analyze zero-day malware.