Skip to main content
Mallory
← Back to News
embedded-device-vulnerabilitywidely-deployed-product-advisoryleaked-secret-api-keyinternet-facing-service-vulnerability

GitHub `Kernel#send()` Flaw Exposed Secrets and Enabled GHES RCE Path

Vulnerability Disclosure · 3 sources · Updated 5mo ago · First seen Apr 11, 2026

GitHub `Kernel#send()` Flaw Exposed Secrets and Enabled GHES RCE Path

A vulnerability tracked as CVE-2024-0200 allowed attackers with organization owner privileges to abuse an unsafe Ruby Kernel#send() call in GitHub’s organization repository settings flow and invoke unintended zero-argument methods on Repository objects. Researchers showed the bug could be used to trigger Repository::GitDependency#nw_fsck() and leak roughly 2 MB of environment variables from a production GitHub.com container, exposing access keys, secrets, and internal configuration because spawned git processes inherited the parent environment.

The issue affected GitHub.com and GitHub Enterprise Server (GHES) instances with GitHub Actions enabled, but the impact was more severe on GHES. STAR Labs reported that leaked variables on GHES could include ENTERPRISE_SESSION_SECRET and other Marshal-related secrets, which could be chained with forged Rails session cookies and an unsafe Marshal.load path to achieve remote code execution. GitHub hotfixed GitHub.com on December 26, 2023, and later released a patch and advisory, while recommended mitigations included allowlisting the rid_key parameter, reducing environment variables passed to git processes, rotating exposed secrets, and monitoring repository_items requests for abnormal rid_key values.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

6 events · Dec 26, 2023 – Apr 15, 2024
  1. Apr 15, 20243y ago

    STAR Labs publishes technical write-up of the GitHub vulnerability chain

    STAR Labs publicly detailed the vulnerability chain, exploitation method, impact on GitHub.com and GHES, and detection and mitigation recommendations. The write-up described the environment variable disclosure and the GHES path to remote code execution.

  2. Jan 16, 20243y ago

    GitHub releases patch and public announcement for CVE-2024-0200

    GitHub published a patch and advisory for CVE-2024-0200, covering affected GitHub Enterprise Server deployments. The announcement disclosed the vulnerability and made remediation available to customers.

  3. Jan 16, 20243y ago

    Research shows GHES exposure could lead to remote code execution

    Analysis of GitHub Enterprise Server showed that leaked environment variables could include ENTERPRISE_SESSION_SECRET or a Marshal-related secret, which could be combined with forged Rails session cookies and an unsafe Marshal deserialization sink to achieve remote code execution. This extended the impact beyond information disclosure on GitHub.com.

  4. Dec 26, 20233y ago

    GitHub hotfixes GitHub.com for CVE-2024-0200

    GitHub applied a hotfix to GitHub.com during the Christmas holiday period to remediate the vulnerability later assigned CVE-2024-0200. The fix addressed the unsafe method invocation path that enabled environment variable disclosure.

  5. Dec 26, 20233y ago

    Vulnerability used to leak GitHub.com container environment variables

    The researcher exploited the flaw on GitHub.com by invoking Repository::GitDependency#nw_fsck(), disclosing roughly 2 MB of environment variables from a production git worker container. The leaked data included numerous access keys, secrets, and internal configuration values inherited by spawned git processes.

  6. Dec 26, 20233y ago

    Researcher discovers GitHub send() flaw exposing repository method calls

    Ngo Wei Lin identified a vulnerability in GitHub's Organizations::Settings::RepositoryItemsComponent where a user-controlled parameter was passed to Ruby's Kernel#send(), enabling zero-argument arbitrary method invocation on Repository-related objects. The issue affected GitHub.com and GitHub Enterprise Server instances with GitHub Actions enabled and required organization owner privileges.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Github Enterprise Server

Organizations

1 linked
GitHub

Breaches

1 linked
GITHUB-2023-12
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.