-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CWEs, CWE version and CWE Weakness clarification #738
CWEs, CWE version and CWE Weakness clarification #738
Conversation
- addresses parts of oasis-tcs#660 - add `version` as new required field to `cwe`
- addresses parts of oasis-tcs#660 - adopt prose to reflect schema - add CSAF 2.0 to CSAF 2.1 conversion rule - copy conversion rule to CVRF CSAF converter
- addresses parts of oasis-tcs#660 - adopt testdata to reflect current version of the schema - adopt examples to reflect current version of the schema
- addresses parts of oasis-tcs#660 - add invalid examples for 6.1.11 - add valid examples for 6.1.11 - explicitly state in 6.1.11 that CWE Views and Categories are not valid
- addresses parts of oasis-tcs#154 - state explicit how to handle CWE categories and views
- addresses parts of oasis-tcs#530 - wrap CWE into a list to allow multiple CWEs per vulnerability
- addresses parts of oasis-tcs#530, oasis-tcs#154 - adopt prose to reflect schema - remove conversion rule for CVRF CSAF converter - reorder CVRF CSAF converter rules regarding CWEs - clarify warning regarding conversion of CWE category and view
- addresses parts of oasis-tcs#530 - adopt test 6.1.11 to reflect schema
- addresses parts of oasis-tcs#530 - adopt examples to reflect schema - adopt testdata to reflect schema
- addresses parts of oasis-tcs#530, oasis-tcs#660 - add `/vulnerabilities[]/cwes[]/version` to guidance on size - add `/vulnerabilities[]/cwes` to guidance on size - adopt pathes to match schema
- addresses parts of oasis-tcs#530 - add invalid example for 6.1.11 - add valid example for 6.1.11
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should consider extending the cwe collector more directly and allowing the external IDs (CWE IDs) to be keys in an object.
csaf_2.1/prose/edit/src/schema-elements-02-props-03-vulnerabilities.md
Outdated
Show resolved
Hide resolved
csaf_2.1/test/validator/data/informative/oasis_csaf_tc-csaf_2_1-2024-6-3-04-02.json
Show resolved
Hide resolved
- addresses review comment from oasis-tcs#738 - clarify that invalid CWEs MUST omitted - use RFC 2119 language
- addresses review comment from oasis-tcs#738 - convert abbreviation back to singular (from plural)
@sthagen Thank you for the review. Please see my comments. |
As we are still discussing the possible solutions, I set this back to draft. |
- addresses review comment from oasis-tcs#738 - clarify that an order of CWEs is expected
@sthagen Please see the suggested wording regarding the order of CWEs. |
@mprpic Please review as well. |
csaf_2.1/prose/edit/src/schema-elements-02-props-03-vulnerabilities.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ship it! 😁
- addresses review comment from oasis-tcs#738 - simplify the statement of ordered CWEs Co-authored-by: Martin Prpič <[email protected]>
The motion to accept the pull request #738 "CWEs, CWE version and CWE Weakness clarification" as suggested in github.com//pull/738 and include it into CSAF 2.1, has passed. It automatically carried on 2024-06-07 23:00 UTC. |
40a2236
into
oasis-tcs:editor-revision-2024-05-29
version
as new required field tocwe