|
53 | 53 | "type": "string", |
54 | 54 | "pattern": "^CVE-[0-9]{4}-[0-9]{4,19}$" |
55 | 55 | }, |
| 56 | + "cpe22and23": { |
| 57 | + "type": "string", |
| 58 | + "description":"Common Platform Enumeration (CPE) Name in either 2.2 or 2.3 format", |
| 59 | + "pattern": "([c][pP][eE]:/[AHOaho]?(:[A-Za-z0-9._\\-~%]*){0,6})|(cpe:2\\.3:[aho*\\-](:(((\\?*|\\*?)([a-zA-Z0-9\\-._]|(\\\\[\\\\*?!\"#$%&'()+,/:;<=>@\\[\\]\\^`{|}~]))+(\\?*|\\*?))|[*\\-])){5}(:(([a-zA-Z]{2,3}(-([a-zA-Z]{2}|[0-9]{3}))?)|[*\\-]))(:(((\\?*|\\*?)([a-zA-Z0-9\\-._]|(\\\\[\\\\*?!\"#$%&'()+,/:;<=>@\\[\\]\\^`{|}~]))+(\\?*|\\*?))|[*\\-])){4})", |
| 60 | + "minLength": 1, |
| 61 | + "maxLength": 2048 |
| 62 | + }, |
| 63 | + "cpe23": { |
| 64 | + "type": "string", |
| 65 | + "description":"Common Platform Enumeration (CPE) Name in 2.3 format", |
| 66 | + "pattern": "(cpe:2\\.3:[aho*\\-](:(((\\?*|\\*?)([a-zA-Z0-9\\-._]|(\\\\[\\\\*?!\"#$%&'()+,/:;<=>@\\[\\]\\^`{|}~]))+(\\?*|\\*?))|[*\\-])){5}(:(([a-zA-Z]{2,3}(-([a-zA-Z]{2}|[0-9]{3}))?)|[*\\-]))(:(((\\?*|\\*?)([a-zA-Z0-9\\-._]|(\\\\[\\\\*?!\"#$%&'()+,/:;<=>@\\[\\]\\^`{|}~]))+(\\?*|\\*?))|[*\\-])){4})", |
| 67 | + "minLength": 1, |
| 68 | + "maxLength": 2048 |
| 69 | + }, |
56 | 70 | "orgId": { |
57 | 71 | "description": "A UUID for an organization participating in the CVE program. This UUID can be used to lookup the organization record in the user registry service.", |
58 | 72 | "$ref": "#/definitions/uuidType" |
|
196 | 210 | }, |
197 | 211 | "cpes": { |
198 | 212 | "type": "array", |
199 | | - "description": "Affected products defined by CPE. This is an array of CPE values (vulnerable and not), we use an array so that we can make multiple statements about the same version and they are separate (if we used a JSON object we'd essentially be keying on the CPE name and they would have to overlap). Also, this allows things like cveDataVersion or cveDescription to be applied directly to the product entry. This also allows more complex statements such as \"Product X between versions 10.2 and 10.8\" to be put in a machine-readable format. As well since multiple statements can be used multiple branches of the same product can be defined here.", |
| 213 | + "description": "Affected products defined by CPE. This is an array of CPE values (vulnerable and not), we use an array so that we can make multiple statements about the same version and they are separate (if we used a JSON object we'd essentially be keying on the CPE name and they would have to overlap). Also, this allows things like cveDataVersion or cveDescription to be applied directly to the product entry. This also allows more complex statements such as \"Product X between versions 10.2 and 10.8\" to be put in a machine-readable format. As well since multiple statements can be used multiple branches of the same product can be defined here. NOTE: Consider using the newer cpeApplicability block for defining CPE data using the CPE Applicability Language which includes more options for defining CPE Names.", |
200 | 214 | "uniqueItems": true, |
201 | 215 | "items": { |
202 | 216 | "title": "CPE Name", |
203 | | - "type": "string", |
204 | 217 | "description":"Common Platform Enumeration (CPE) Name in either 2.2 or 2.3 format", |
205 | | - "pattern": "([c][pP][eE]:/[AHOaho]?(:[A-Za-z0-9._\\-~%]*){0,6})|(cpe:2\\.3:[aho*\\-](:(((\\?*|\\*?)([a-zA-Z0-9\\-._]|(\\\\[\\\\*?!\"#$%&'()+,/:;<=>@\\[\\]\\^`{|}~]))+(\\?*|\\*?))|[*\\-])){5}(:(([a-zA-Z]{2,3}(-([a-zA-Z]{2}|[0-9]{3}))?)|[*\\-]))(:(((\\?*|\\*?)([a-zA-Z0-9\\-._]|(\\\\[\\\\*?!\"#$%&'()+,/:;<=>@\\[\\]\\^`{|}~]))+(\\?*|\\*?))|[*\\-])){4})", |
206 | | - "minLength": 1, |
207 | | - "maxLength": 2048 |
| 218 | + "$ref": "#/definitions/cpe22and23" |
208 | 219 | } |
209 | 220 | }, |
210 | 221 | "modules": { |
|
487 | 498 | "required": ["orgId"], |
488 | 499 | "additionalProperties": false |
489 | 500 | }, |
| 501 | + "cpeApplicabilityElement": { |
| 502 | + "description": "Affected products defined using an implementation of the CPE Applicability Language, mostly copied/forked from the NIST NVD CVE API v2.0 schema (optional). An operator property allows AND or OR logic between CPEs or combinations of CPEs. The negate and vulnerable Boolean properties allow CPEs to be inverted and/or defined as vulnerable or not. Multiple version fields are provided for capturing ranges of products when defining a CPE Match String Range. NOTE: When defining a cpeApplicability block, it is recommended that it align with (as much as possible) the product data provided within the affected block.", |
| 503 | + "properties": { |
| 504 | + "operator": { |
| 505 | + "type": "string", |
| 506 | + "enum": [ |
| 507 | + "AND", |
| 508 | + "OR" |
| 509 | + ] |
| 510 | + }, |
| 511 | + "negate": { |
| 512 | + "type": "boolean" |
| 513 | + }, |
| 514 | + "nodes": { |
| 515 | + "type": "array", |
| 516 | + "items": { |
| 517 | + "$ref": "#/definitions/cpe_node" |
| 518 | + } |
| 519 | + } |
| 520 | + }, |
| 521 | + "required": [ |
| 522 | + "nodes" |
| 523 | + ] |
| 524 | + }, |
| 525 | + "cpe_node": { |
| 526 | + "description": "Defines a CPE configuration node in an applicability statement.", |
| 527 | + "properties": { |
| 528 | + "operator": { |
| 529 | + "type": "string", |
| 530 | + "enum": [ |
| 531 | + "AND", |
| 532 | + "OR" |
| 533 | + ] |
| 534 | + }, |
| 535 | + "negate": { |
| 536 | + "type": "boolean" |
| 537 | + }, |
| 538 | + "cpeMatch": { |
| 539 | + "type": "array", |
| 540 | + "items": { |
| 541 | + "$ref": "#/definitions/cpe_match" |
| 542 | + } |
| 543 | + } |
| 544 | + }, |
| 545 | + "required": [ |
| 546 | + "operator", |
| 547 | + "cpeMatch" |
| 548 | + ] |
| 549 | + }, |
| 550 | + "cpe_match": { |
| 551 | + "description": "CPE match string or range", |
| 552 | + "type": "object", |
| 553 | + "properties": { |
| 554 | + "vulnerable": { |
| 555 | + "type": "boolean" |
| 556 | + }, |
| 557 | + "criteria": { |
| 558 | + "$ref": "#/definitions/cpe23" |
| 559 | + }, |
| 560 | + "matchCriteriaId": { |
| 561 | + "$ref": "#/definitions/uuidType" |
| 562 | + }, |
| 563 | + "versionStartExcluding": { |
| 564 | + "$ref": "#/definitions/version" |
| 565 | + }, |
| 566 | + "versionStartIncluding": { |
| 567 | + "$ref": "#/definitions/version" |
| 568 | + }, |
| 569 | + "versionEndExcluding": { |
| 570 | + "$ref": "#/definitions/version" |
| 571 | + }, |
| 572 | + "versionEndIncluding": { |
| 573 | + "$ref": "#/definitions/version" |
| 574 | + } |
| 575 | + }, |
| 576 | + "required": [ |
| 577 | + "vulnerable", |
| 578 | + "criteria" |
| 579 | + ], |
| 580 | + "additionalProperties": false |
| 581 | + }, |
490 | 582 | "cnaPublishedContainer": { |
491 | 583 | "description": "An object containing the vulnerability information provided by a CVE Numbering Authority (CNA) for a published CVE ID. There can only be one CNA container per CVE record since there can only be one assigning CNA. The CNA container must include the required information defined in the CVE Rules, which includes a product, version, problem type, prose description, and a reference.", |
492 | 584 | "type": "object", |
|
514 | 606 | "affected": { |
515 | 607 | "$ref": "#/definitions/affected" |
516 | 608 | }, |
| 609 | + "cpeApplicability": { |
| 610 | + "type": "array", |
| 611 | + "items": { |
| 612 | + "$ref": "#/definitions/cpeApplicabilityElement" |
| 613 | + } |
| 614 | + }, |
517 | 615 | "problemTypes": { |
518 | 616 | "$ref": "#/definitions/problemTypes" |
519 | 617 | }, |
|
620 | 718 | "affected": { |
621 | 719 | "$ref": "#/definitions/affected" |
622 | 720 | }, |
| 721 | + "cpeApplicability": { |
| 722 | + "type": "array", |
| 723 | + "items": { |
| 724 | + "$ref": "#/definitions/cpeApplicabilityElement" |
| 725 | + } |
| 726 | + }, |
623 | 727 | "problemTypes": { |
624 | 728 | "$ref": "#/definitions/problemTypes" |
625 | 729 | }, |
|
0 commit comments