Bug 2184905 (CVE-2023-25823) - CVE-2023-25823 gradio: user could access other users shared Gradio demos
Summary: CVE-2023-25823 gradio: user could access other users shared Gradio demos
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2023-25823
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2184906
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-06 07:16 UTC by Dhananjay Arunesh
Modified: 2023-04-06 12:39 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-06 12:39:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2023-04-06 07:16:25 UTC
Gradio is an open-source Python library to build machine learning and data science demos and web applications. Versions prior to 3.13.1 contain Use of Hard-coded Credentials. When using Gradio's share links (i.e. creating a Gradio app and then setting 'share=True'), a private SSH key is sent to any user that connects to the Gradio machine, which means that a user could access other user's shared Gradio demos. From there, other exploits are possible depending on the level of access/exposure the Gradio app provides. This issue is patched in version 3.13.1, however, users are recommended to update to 3.19.1 or later where the FRP solution has been properly tested.

References:
https://github.com/gradio-app/gradio/security/advisories/GHSA-3x5j-9vwr-8rr5

Comment 1 Dhananjay Arunesh 2023-04-06 07:16:44 UTC
Created gradio tracking bugs for this issue:

Affects: epel-8 [bug 2184906]

Comment 2 Product Security DevOps Team 2023-04-06 12:39:17 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.