CNA scope conflict improvement #6612
Open
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Disagree. We still handled it by coordinating with the other CNA, we just didn't assign it ourselves. This exists because we need maintainers not to go run off themselves and have CVEs assigned. |
Kevin-CB
commented
Aug 14, 2023
| @@ -101,7 +101,7 @@ The following is a rough approximation of the typical recommended lifecycle of a | |||
| .. The security team provides a private repository for that work in the `jenkinsci-cert` GitHub organization. | |||
| .. Work usually happens on a branch, and a corresponding pull request will be used for review. | |||
| . A *date and time of the release is coordinated* between the security team and maintainers. | |||
| The security team handles CVE ID assignment, advance notification of users, and creation of the security advisory. | |||
| The security team handles CVE ID assignment (in cases where there is no CNA scope conflict), advance notification of users, and creation of the security advisory. | |||
There was a problem hiding this comment.
We still handled it by coordinating with the other CNA, we just didn't assign it ourselves.
Do you prefer an approach like this one ,or do you think it should not be mentioned?
Suggested change
| The security team handles CVE ID assignment (in cases where there is no CNA scope conflict), advance notification of users, and creation of the security advisory. | |
| The security team handles CVE ID assignment (assignment may require coordination with another CNA in case of a scope conflict), advance notification of users, and creation of the security advisory. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We recently had a misunderstanding regarding the assignment of CVEs when there's a scope conflict with another CNA.
(see SECURITY-3141)