[GHSA-xxcj-rhqg-m46g] Update AV, AC, and UI in CVSS 3.x #5169
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.
After reviewing the description and exploitation details for CVE-2022-41889 / GHSA-xxcj-rhqg-m46g, I believe the current CVSS 3.x vector assignment might not fully align with the nature of the vulnerability. The vulnerability targets the same module
tf.compat.v1.*
as CVE-2022-29205 / GHSA-54ch-gjq5-4976, and the exploitation path appears comparable. However, the following CVSS metrics for CVE-2022-41889 seem to overstate its complexity and attack requirements: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:HMore specifically:
tf.compat.v1.*
within a local execution context. There is no evidence suggesting that network access (i.e.,AV:N
) is a prerequisite.AC:H
.I believe the correct vector should be: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, which matches the vector for CVE-2022-29205; it involves the almost identical exploration scenario.