CVE-2024-4254VulnerabilityPublished 4 Jun 2024Updated 21 Oct 2025

CVE-2024-4254: gradio-app/gradio · Invocation of Process Using Visible Sensitive Information

Affects gradio-app/gradioSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-4254, organizations should immediately audit GitHub Actions workflows to identify any that run code from forks with access to secrets. Specifically, the 'deploy-website.yml' workflow should be modified to avoid checking out and executing code from untrusted forks. Implement the following measures: 1) Use the 'pull_request_target' event cautiously, as it runs workflows in the context of the base repository and can expose secrets; prefer 'pull_request' event which runs in the fork context without secrets. 2) Restrict workflow permissions by setting 'permissions' to least privilege, removing write or secret access where unnecessary. 3) Use GitHub's 'workflow_run' or manual approval gates to control execution of workflows that require secrets. 4) Employ environment protection rules and required reviewers before allowing workflows with secrets to run. 5) Rotate exposed secrets immediately if compromise is suspected. 6) Educate developers on secure CI/CD practices and avoid embedding secrets in workflows. 7) Consider using GitHub's OIDC token-based authentication to reduce static secret usage. 8) Monitor workflow runs and logs for suspicious activity. These steps will reduce the risk of secret exfiltration via malicious pull requests and improve overall CI/CD security posture.

Description

The 'deploy-website.yml' workflow in the gradio-app/gradio repository, specifically in the 'main' branch, is vulnerable to secrets exfiltration due to improper authorization. The vulnerability arises from the workflow's explicit checkout and execution of code from a fork, which is unsafe as it allows the running of untrusted code in an environment with access to push to the base repository and access secrets. This flaw could lead to the exfiltration of sensitive secrets such as GITHUB_TOKEN, HF_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, COMMENT_TOKEN, AWSACCESSKEYID, AWSSECRETKEY, and VERCEL_TOKEN. The vulnerability is present in the workflow file located at https://github.com/gradio-app/gradio/blob/72f4ca88ab569aae47941b3fb0609e57f2e13a27/.github/workflows/deploy-website.yml.

Impact

For European organizations using gradio-app or integrating its workflows into their CI/CD pipelines, this vulnerability poses a substantial risk. The exfiltration of secrets such as AWS keys and deployment tokens can lead to unauthorized access to cloud infrastructure, enabling data theft, service disruption, or further lateral movement within corporate networks. Compromise of GITHUB_TOKEN can allow attackers to push malicious code, alter repository contents, or escalate privileges within the development environment. Organizations relying on Hugging Face or Vercel services for AI or web deployments may face service outages or data leaks. The breach of these secrets can also undermine compliance with GDPR and other data protection regulations, leading to legal and reputational consequences. Since the vulnerability exploits GitHub Actions workflows, organizations heavily dependent on GitHub for development and deployment are particularly vulnerable. The risk is amplified in collaborative open-source projects or enterprises accepting external contributions without strict workflow security controls. Overall, the vulnerability threatens confidentiality and integrity of critical development and deployment assets, potentially causing significant operational and financial damage.

Summary

CVE-2024-4254 is a vulnerability classified under CWE-214 (Invocation of Process Using Visible Sensitive Information) affecting the 'deploy-website.yml' GitHub Actions workflow in the gradio-app/gradio repository. The core issue is that the workflow explicitly checks out and executes code from forks, which are untrusted sources, without sufficient authorization or security controls. This allows an attacker who submits a pull request from a forked repository to inject malicious code that runs within the GitHub Actions environment. Since the workflow has access to sensitive secrets such as GITHUB_TOKEN, HF_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, COMMENT_TOKEN, AWSACCESSKEYID, AWSSECRETKEY, and VERCEL_TOKEN, the malicious code can exfiltrate these secrets. These tokens provide access to critical resources including GitHub repository management, Hugging Face services, Vercel deployments, and AWS cloud infrastructure. The vulnerability is particularly dangerous because it requires no privileges or authentication from the attacker beyond submitting a pull request, and user interaction (such as approving or triggering the workflow) is needed to execute the malicious code. The CVSS score of 7.1 reflects a high severity due to the ease of exploitation and the high confidentiality impact. Although no known exploits are reported in the wild, the risk remains significant given the sensitive nature of the exposed secrets. The vulnerability highlights the risks of running workflows that execute untrusted code with access to secrets, a common misconfiguration in CI/CD pipelines. The affected workflow file is publicly accessible, enabling attackers to analyze and craft targeted exploits.

CWE-214Invocation of Process Using Visible Sensitive Information (opens in a new tab)
Base weakness
A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.2 (opens in a new tab)
V14.3.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

huntr.com/bounties/59873fbd-5698-4ec3-87f9-5d70c6055d01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Oct 2025, 13:39 UTC

WeaknessesCWE-214

Technical details

References

Community reviews

Related threats