Add a formal semver 2.0.0 version type

.github/workflows/validate-schema.yml

@@ -36,3 +36,7 @@ jobs:
           ajv validate -c ajv-formats -s "${CVE_SCHEMA_DIR}/docs/CVE_Record_Format_bundled.json" -d "${CVE_SCHEMA_DIR}/docs/full-record-advanced-example.json"
           ajv validate -c ajv-formats -s "${CVE_SCHEMA_DIR}/docs/CVE_Record_Format_bundled_cnaPublishedContainer.json" -d "${CVE_SCHEMA_DIR}/docs/cnaContainer-advanced-example.json"
           ajv validate -c ajv-formats -s "${CVE_SCHEMA_DIR}/docs/CVE_Record_Format_bundled_cnaPublishedContainer.json" -d "${CVE_SCHEMA_DIR}/docs/cnaContainer-basic-example.json"
+      # Run semver 2.0.0 tests
+          ajv test -c ajv-formats -s "${CVE_SCHEMA_DIR}/docs/CVE_Record_Format_bundled.json" -d "${CVE_SCHEMA_DIR}/support/tests/valid/valid-semver-2-0-0/*.json" --valid
+          ajv test -c ajv-formats -s "${CVE_SCHEMA_DIR}/docs/CVE_Record_Format_bundled.json" -d "${CVE_SCHEMA_DIR}/support/tests/invalid/invalid-semver-2-0-0/*.json" --invalid
+

rfds/0000-formalize-semver-version-type.md

@@ -0,0 +1,81 @@
+# Add a formal semver 2.0.0 version type
+
+| Field            | Value  |
+|:-----------------|:-------|
+| RFD Submitter    | Jon Moroney |
+| RFD Pull Request | [RFD #0000](https://github.com/CVEProject/cve-schema/pull/371) |
+
+## Summary
+[summary]: #summary
+
+Introduce a new semantic versioning version type for the machine readable `versions` array. The goal of this addition is to provide consumers of CVE records with version information which is interoperable with off the shelf semantic versioning compatible tools. The proposed change includes schema based validation to ensure submitted records conform to the semver specification as well as tests to ensure conformity.
+
+## Problem Statement
+[problem-statement]: #problem-statement
+
+Today the `versions` array allows for a number of typed version fields which should inform the reader how to interpret the data. Alas, there is no validation that a record producer must conform to and as a result the version types have been used inconsistently. At time of writing a consumer reading the semantic versioning type in particular has about a [44% chance of the data conforming to the semantic versioning specification](https://darakian.github.io/2025/06/04/parsing-semver-from-cve.html).
+
+As a result consumers of CVE records cannot build reliable automation from the data in the record itself. Multiple sub-patterns do exist, but there is canonical list of them nor is there any guarantee of their stability. This leads to increased operational complexity in vulnerability management and potentially to vulnerabilities going unresolved.
+
+Failing to adopt stricter datatypes will maintain the status quo which is generally accepted to be lacking.
+
+## Proposed Solution
+[proposed-solution]: #proposed-solution
+
+The proposed change adds a new `semver-2.0.0-version` pattern and five new properties for expressing version ranges. The parameters are `exactly`, `inclusiveLowerBound`, `exclusiveLowerBound`, `inclusiveUpperBound`, and `exclusiveUpperBound` and map to the mathematics operators `=`, `>=`, `>`, `<=`, and `<`. These parameters are only expected to be used with the `semver-2.0.0` version type. Validation is proved in the form of a regular expression which is taken directly from semver.org in order to ensure interoperability.
+
+## Examples
+[examples]: #examples
+
+Examples are provided as tests and may be viewed in the valid and invalid semver-2-0-0 subdirectories here:
+https://github.com/CVEProject/cve-schema/tree/0dc04e2a9adb9e3d50409051ce1d006d79b57a90/schema/support/tests
+
+## Impact Assessment
+[impact-assessment]: #impact-assessment
+
+This proposal has been designed to be very low impact. In the base case both record producers and record consumers can simply ignore the new data type. Adoption of the new data type into systems that process CVE records should be quite straight forward as semantic versioning is well supported across many languages. Once records begin to be produced with `semver-2.0.0` values a record consumer will be able to build reliable vulnerability managment automation based on the data.
+
+## Compatibility and Migration
+[compatibility-and-migration]: #compatibility-and-migration
+
+This change adds one new, optional, value to the `versions` array and should be completely backwards compatible as no prior data formats are altered. The version type is currently arbitrary and so record providers are free to populate anything in that field, however no currently published records have used `semver-2.0.0`.
+
+Both consumers are producers will need to update their code/process in order to make use of the new field. Should there be a desire to coordinate a migration an addition could be made to this RFD with guidance both for record producer and consumers, but off the shelf, semver compatible tools are expected to work.
+
+Existence of the new version type should be communicated to stakeholders upon the RFDs acceptance.
+
+## Success Metrics
+[success-metrics]: #success-metrics
+
+6+ months after the acceptance and adoption of this RFD process, the QWG should conduct a review of published CVE records to assess usage of the new version type. Additionally the QWG should solicit a survey to QWG members and outside CVE stakeholders about the perceived value of the new type. If there is low/no usage as well as a poor qualitative perception then the effort should be considered a failure and discussion of a rollback should be considered.
+
+If there is consistent measured usage as well as positive qualitative perception then the effort should be considered a success. Anything between these two polls will require more qualitative analysis, but it is the RFD author's opinion that if there is a lack of consensus then the effort should by default be considered a failure.
+
+A roll back of this RFD would consist of a removal of the `semver-2.0.0` version type and associated tests.
+
+## Supporting Data or Research
+[supporting-data-or-research]: #supporting-data-or-research
+
+
+## Related Issues or Proposals
+[related-issues-or-proposals]: #related-issues-or-proposals
+
+This change originated out of a conversation detailing the shortcomings of the current versioning system here:
+https://github.com/CVEProject/cve-schema/issues/362
+
+An alternative to adopting this RFD would be to not adopt it.
+
+## Recommended Priority
+[recommended-priority]: #recommended-priority
+
+Medium
+
+## Unresolved Questions
+[unresolved-questions]: #unresolved-questions
+
+None currently.
+
+## Future Possibilities
+[future-possibilities]: #future-possibilities
+
+Other common versioning types could have new, validated versions provided via subsequent RFDs.

schema/CVE_Record_Format.json

@@ -98,6 +98,11 @@
             "minLength": 1,
             "maxLength": 1024
         },
+        "semver-2.0.0-version": {
+            "description": "A semver 2.0.0 compatible version",
+            "type": "string",
+            "pattern": "^(0|[1-9]\\d*)\\.(0|[1-9]\\d*)\\.(0|[1-9]\\d*)(?:-((?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\\.(?:0|[1-9]\\d*|\\d*[a-zA-Z-][0-9a-zA-Z-]*))*))?(?:\\+([0-9a-zA-Z-]+(?:\\.[0-9a-zA-Z-]+)*))?$"
+        },
         "status": {
             "description": "The vulnerability status of a given version or range of versions of a product. The statuses 'affected' and 'unaffected' indicate that the version is affected or unaffected by the vulnerability. The status 'unknown' indicates that it is unknown or unspecified whether the given version is affected. There can be many reasons for an 'unknown' status, including that an investigation has not been undertaken or that a vendor has not disclosed the status.",
             "type": "string",
@@ -299,10 +304,40 @@
                                 "maxProperties": 3
                             },
                             {
-                                "required": ["version", "status", "versionType", "lessThan"]
+                                "required": ["status", "versionType", "lessThan"]
                             },
                             {
-                                "required": ["version", "status", "versionType", "lessThanOrEqual"]
+                                "required": ["status", "versionType", "lessThanOrEqual"]
+                            },
+                            {
+                                "required": ["status", "versionType"],
+                                "maxProperties": 3,
+                                "properties": {"versionType": { "const": "semver-2.0.0" }},
+                                "oneOf": [
+                                    {"required": ["exactly"]},
+                                    {"required": ["inclusiveLowerBound"]},
+                                    {"required": ["exclusiveLowerBound"]},
+                                    {"required": ["inclusiveUpperBound"]},
+                                    {"required": ["exclusiveUpperBound"]}
+                                ]
+                            },
+                            {
+                                "required": ["status", "versionType", "inclusiveLowerBound"],
+                                "maxProperties": 4,
+                                "properties": {"versionType": { "const": "semver-2.0.0" }},
+                                "oneOf": [
+                                    {"required": ["inclusiveUpperBound"]},
+                                    {"required": ["exclusiveUpperBound"]}
+                                ]
+                            },
+                            {
+                                "required": ["status", "versionType", "exclusiveLowerBound"],
+                                "maxProperties": 4,
+                                "properties": {"versionType": { "const": "semver-2.0.0" }},
+                                "oneOf": [
+                                    {"required": ["inclusiveUpperBound"]},
+                                    {"required": ["exclusiveUpperBound"]}
+                                ]
                             }
                         ],
                         "properties": {
@@ -336,6 +371,27 @@
                                 "description": "The inclusive upper limit of the range. This is the greatest version contained in the range. Only one of lessThan and lessThanOrEqual should be specified. For example, `{version: 1.0, lessThanOrEqual: 1.3}` covers all versions from 1.0 up to and including 1.3.",
                                 "$ref": "#/definitions/version"
                             },
+                            "exactly": {
+                                "description": "A single semver 2.0.0 version to mark",
+                                "$ref": "#/definitions/semver-2.0.0-version"
+                            },
+                            "inclusiveLowerBound": {
+                                "description": "A valid semver 2.0.0 value used as a lower bound. Explicitly also affected.",
+                                "$ref": "#/definitions/semver-2.0.0-version"
+                            },
+                            "exclusiveLowerBound": {
+                                "description": "A valid semver 2.0.0 value used as a lower bound. Explicitly not affected.",
+                                "$ref": "#/definitions/semver-2.0.0-version"
+                            },
+                            "inclusiveUpperBound": {
+                                "description": "A valid semver 2.0.0 value used as an upper bound. Explicitly also affected.",
+                                "$ref": "#/definitions/semver-2.0.0-version"
+
+                            },
+                            "exclusiveUpperBound": {
+                                "description": "A valid semver 2.0.0 value used as an upper bound. Explicitly not affected.",
+                                "$ref": "#/definitions/semver-2.0.0-version"
+                            },
                             "changes": {
                                 "type": "array",
                                 "description": "A list of status changes that take place during the range. The array should be sorted in increasing order by the 'at' field, according to the versionType, but clients must re-sort the list themselves rather than assume it is sorted.",
@@ -349,7 +405,9 @@
                                     "properties": {
                                         "at": {
                                             "description": "The version at which a status change occurs.",
-                                            "$ref": "#/definitions/version"
+                                            "oneOf": [
+                                                {"$ref": "#/definitions/version"}
+                                            ]
                                         },
                                         "status": {
                                             "description": "The new status in the range starting at the given version.",

schema/docs/versions.md

@@ -288,6 +288,78 @@ Now that we know how to encode version objects, that would be written as:
 		}
 	]
 
+### Version Types
+
+#### Semantic versioning 2.0.0
+
+Type identifier: `semver-2.0.0`
+Formally specified here at https://semver.org/spec/v2.0.0.html
+`semver-2.0.0` is type introduced to formally specify usage of semantic versioning. 
+
+`semver-2.0.0` in its simplest form is a dot separated triple. eg `1.2.3`. The three parts have names with the first being the `MAJOR`, the second being `MINOR` and the third `PATCH`. The [Semantic](https://en.wikipedia.org/wiki/Semantics) meaning of each is described as 
+1. MAJOR version when you make incompatible API changes
+2. MINOR version when you add functionality in a backward compatible manner
+3. PATCH version when you make backward compatible bug fixes
+This triple can be extended with either a `-` or a `+` or with both for `pre-release` and `build` identifiers.
+The triple can only be populated with non-negative integers and must not contain leading zeros. 
+Ordering of the triple is determined by the first difference when comparing each of these identifiers from left to right as follows: Major, minor, and patch versions are always compared numerically.
+Full ordering for pre-releases and builds are described in the semver document [here](https://semver.org/spec/v2.0.0.html#spec-item-11).
+While the triple can only contain numeric values the `pre-release` and `build` are free to be alpha numeric. 
+A complete definition of this version type can be viewed here
+https://semver.org/spec/v2.0.0.html#backusnaur-form-grammar-for-valid-semver-versions
+
+The `semver-2.0.0` version type has five possible parameters which may be used to define either a single version or a continuous range. The parameters are `exactly`, `inclusiveLowerBound`, `exclusiveLowerBound`, `inclusiveUpperBound`, and `exclusiveUpperBound`. The use of `exactly` alone defines a single version when used alone. The other parameters are used to define a range of values which are .
+
+##### Example
+
+```
+"affected": [
+        {
+          "vendor": "Example.org",
+          "product": "Example Enterprise",
+          "versions": [
+            {
+              "versionType": "semver-2.0.0",
+              "status": "affected",
+              "inclusiveLowerBound": "1.2.3-alpha",
+              "inclusiveUpperBound": "2.3.4+build17"
+            }
+            {
+              "versionType": "semver-2.0.0",
+              "status": "unaffected",
+              "exclusiveLowerBound": "3.4.5-beta",
+              "exclusiveUpperBound": "4.5.6+assembly88"
+            }
+            {
+              "versionType": "semver-2.0.0",
+              "status": "affected",
+              "exactly": "5.6.7-gamma",
+            }
+            {
+              "versionType": "semver-2.0.0",
+              "status": "affected",
+              "exactly": "6.7.8-delta",
+            }
+            {
+              "versionType": "semver-2.0.0",
+              "status": "affected",
+              "exclusiveUpperBound": "1.0.0",
+            }
+            {
+              "versionType": "semver-2.0.0",
+              "status": "unknown",
+              "inclusiveLowerBound": "9.0.0",
+            }
+          ],
+        }
+      ],
+```
+
+#### Explainer
+
+A `semver-2.0.0` version is expressed as either a range or as a single exact version. Chaining multiple `semver-2.0.0` versions can be done to express more complex ranges. A `semver-2.0.0` range must begin with a lower bound which is followed by an upper bound. Each bound may be either inclusive or exclusive. These terms map as `exclusiveUpperBound` to `<`, `inclusiveUpperBound` to `<=`, `exclusiveLowerBound` to `>`, `inclusiveLowerBound` to `>=` and `exactly` to `=`. Thus the first example above could be rewritten as `>= 1.2.3-alpha, <= 2.3.4+build17`.
+
+
 ## Version Status Changes
 
 As presented in the previous section,

schema/support/Node_Validator/build.js

@@ -3,7 +3,7 @@ const path = require("path")
 const Ajv = require('ajv').default;
 const standaloneCode = require("ajv/dist/standalone").default
 const addFormats = require('ajv-formats').default;
-const schema = require("../../docs/CVE_JSON_bundled.json")
+const schema = require("../../docs/CVE_Record_Format_bundled.json")
 
 function reduceSchema(o) {
     for(prop in o) {

schema/support/tests/invalid/invalid-semver-2-0-0/asterisk-usage.json

@@ -0,0 +1,51 @@
+{
+  "dataType": "CVE_RECORD",
+  "dataVersion": "5.1",
+  "cveMetadata": {
+    "cveId": "CVE-1900-1234",
+    "assignerOrgId": "b3476cb9-2e3d-41a6-98d0-0f47421a65b6",
+    "state": "PUBLISHED"
+  },
+  "containers": {
+    "cna": {
+      "providerMetadata": {
+        "orgId": "b3476cb9-2e3d-41a6-98d0-0f47421a65b6"
+      },
+      "problemTypes": [
+        {
+          "descriptions": [
+            {
+              "lang": "en",
+              "description": "CWE-78 OS Command Injection"
+            }
+          ]
+        }
+      ],
+      "affected": [
+        {
+          "vendor": "Example.org",
+          "product": "Example Enterprise",
+          "versions": [
+            {
+              "versionType": "semver-2.0.0",
+              "status": "affected",
+              "exactly": "1.2.*"
+            }
+          ],
+          "defaultStatus": "unaffected"
+        }
+      ],
+      "descriptions": [
+        {
+          "lang": "en",
+          "value": "OS Command Injection vulnerability parseFilename function of example.php in the Web Management Interface of Example.org Example Enterprise on Windows, MacOS and XT-4500 allows remote unauthenticated attackers to escalate privileges.\n\nThis issue affects:\n  *  1.0 versions before 1.0.6\n  *  2.1 versions from 2.16 until 2.1.9."
+        }
+      ],
+      "references": [
+        {
+          "url": "https://example.org/ESA-22-11-CVE-1900-1234"
+        }
+      ]
+    }
+  }
+}