vulns.co
/
GKData.io MCP and API Buy me a coffee

GitHub · Injection and untrusted input

GitHub unsafe reflection crossed method and credential boundaries

GitHub.com exposed production-container credentials because user input could select internal operations that should have been restricted. GitHub links this incident to its highest single paid reward of 2023; the researcher's later analysis separately describes code-execution potential on GitHub Enterprise Server, not demonstrated execution on GitHub.com. This historical case shows why applications need to restrict operation selection, limit runtime secrets and distinguish evidence from different deployments.

Read the original writeupUSD 75,000 reported award · Reviewed 2026-10-04

Root cause

User-controlled data could select internal methods beyond the intended set of operations. The researcher traces this unsafe reflection to the point where selection data gained the application’s internal authority; the GHES advisory confirms the weakness class. Authentication and organization ownership limited who could reach it, but did not make unrestricted method selection safe.

Demonstrated impact

GitHub confirms production-container credential exposure and assessed with high confidence that the issue had not been previously exploited and impact was isolated to the researcher. The researcher separately reports GHES code-execution potential; GitHub's GHES advisory corroborates that impact class and requires an authenticated organization-owner account. These sources do not establish code execution on GitHub.com. No secret values or private victim data are retained.

What to check for

  • Constrain dynamic operation selection to an explicit permitted set, with authorization for the selected operation rather than relying only on the caller's authenticated role.
  • Minimize secrets available to each process and define narrow response-data contracts so an unexpected internal result cannot disclose ambient credentials.
  • Treat credential exposure as requiring coordinated rotation and dependency review; design recovery procedures that limit disruption.
  • For 2026 framework reviews, assess input-to-operation authority separately from input format and keep hosted-service observations distinct from self-managed deployment impact.

Award and evidence

USD 75,000Bug Bounty · Vendor Confirmed
How the award was verified, and what the record does not establish

One vendor-reported paid reward linked to this incident, not a program ceiling or total. USD is a contextual inference: the award source uses $ only. GitHub's January 9, 2017 program article, updated June 25, 2021, explicitly uses USD; HackerOne's guidelines version 1.3, updated July 27, 2026, also specify USD. These earlier program-wide and later platform-wide statements are not contemporaneous 2023 payment evidence and do not independently prove this award's currency or settlement. No conflicting denomination was found in the reviewed sources. The retrospective establishes the amount and payment year; no separate award is inferred for the follow-up GHES impact.

  • Payment is vendor-reported, not an independently audited bank transfer. Exact award-decision and payment days are unknown.
  • USD denomination is contextual inference from non-contemporaneous official evidence; neither currency-context source establishes the individual amount or settlement.
  • The researcher describes the GHES execution-impact extension separately from the GitHub.com credential-exposure observation. The precise GHES demonstration and implementation details are not independently verified here.
  • GitHub's assessment of no earlier exploitation is the vendor's investigation conclusion, not an independent guarantee.
  • The record summarizes a patched historical case; review in 2026 does not imply current exposure or grant testing authorization.

Timeline

Published
2024-05-06explicit · Detailed researcher publication and coordinated technical disclosure.
Public Disclosure
2024-01-16explicit · Vendor incident notice; distinct from the later detailed researcher publication.
Reported
2023-12-26explicit · Initial report. The researcher timeline separately dates the GHES execution-impact follow-up to December 28, 2023.
Fixed
2023-12-26explicit · GitHub.com fix only. The vendor incident notice and GHES release notes date GHES patches to January 16, 2024.
Paid
2023explicit · Vendor explicitly says the single reward was paid in 2023; exact payment day and independent settlement evidence are unavailable.
Award Announced
2024-06-11explicit · Publication date of the reviewed award retrospective, updated July 23, 2024; the earliest announcement date is not established.
Mitigated
2023-12-26explicit · Credential rotation began after the GitHub.com fix; this is not a rotation-completion date.

Related cases

All 4 cases in Injection and untrusted input

Sources

  1. GitHub.com's Environment Variables & GHES ShellNgo Wei Lin (Creastery) · reviewed 2026-10-04
  2. 10 years of the GitHub Security Bug Bounty ProgramJill Moné-Corallo / GitHub · reviewed 2026-10-04
  3. Rotating credentials for GitHub.com and new GHES patchesJacob DePriest / GitHub · reviewed 2026-10-04
  4. GitHub Enterprise Server 3.11.3 release notesGitHub · reviewed 2026-10-04
  5. Bug Bounty anniversary promotion: bigger bounties in January and FebruaryNeil Matatall / GitHub · reviewed 2026-10-04
  6. Vulnerability Disclosure Guidelines (Vulnerability Disclosure Standards)HackerOne · reviewed 2026-10-04

Record reviewed 2026-10-04. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software