Skip to content

Duplicate Advisory: Cross-Site Request Forgery in Gradio

Moderate severity GitHub Reviewed Published Mar 21, 2024 to the GitHub Advisory Database • Updated May 21, 2024
Withdrawn This advisory was withdrawn on May 21, 2024

Package

pip gradio (pip)

Affected versions

< 4.19.2

Patched versions

4.19.2

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-48cq-79qq-6f7x. this link is maintained to preserve external references.

Original Description

A Cross-Site Request Forgery gives attackers the ability to upload many large files to a victim, if they are running Gradio locally. To resolve this a PR tightening the CORS rules around Gradio applications has been submitted. In particular, it checks to see if the host header is localhost (or one of its aliases) and if so, it requires the origin header (if present) to be localhost (or one of its aliases) as well.

References

Published by the National Vulnerability Database Mar 21, 2024
Published to the GitHub Advisory Database Mar 21, 2024
Reviewed Mar 22, 2024
Withdrawn May 21, 2024
Last updated May 21, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-3x9g-xfj5-fq84

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.