Skip to content
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

[GHSA-xxcj-rhqg-m46g] Update AV, AC, and UI in CVSS 3.x #5169

Conversation

vulnerability-analyst
Copy link

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:H

More specifically:

  • Attack Vector (AV): The vulnerability only requires the use of quantized tensors in tf.compat.v1.* within a local execution context. There is no evidence suggesting that network access (i.e., AV:N) is a prerequisite.
  • Attack Complexity (AC): The exploitation process for this issue does not appear to involve “a measurable amount of effort in preparation or execution against the vulnerable component,” as defined for AC:H.
  • User Interaction (UI): The description of CVE-2022-41889 does not mention explicit user action (e.g., running a specific script or interacting with an interface). The issue occurs during tensor handling within the vulnerable module, suggesting no user interaction is necessary.

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.

@github-actions github-actions bot changed the base branch from main to vulnerability-analyst/advisory-improvement-5169 January 14, 2025 22:21
@shelbyc
Copy link
Contributor

shelbyc commented Jan 15, 2025

👋 Hi @vulnerability-analyst, I think changing the CVSSv3 value in GHSA-xxcj-rhqg-m46g from CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:H to CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H is reasonable. Because GitHub is responsible for the CVE record for CVE-2022-41889, I will initiate an update to the CVE record too.

@advisory-database advisory-database bot merged commit 23d02eb into github:vulnerability-analyst/advisory-improvement-5169 Jan 15, 2025
2 checks passed
@advisory-database
Copy link
Contributor

Hi @vulnerability-analyst! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants