0x365 - Teknik - Clés privées GitHub App

0x365 - Teknik - Clés privées GitHub App

0x365 - Teknik - GitHub App private keys

Title history
  • 0x365 - Teknik - Clés privées GitHub App — observed on 20261110-0823 UTC (YouTube)
🎙 Gaetan Ferry (interviewed in PolySécure Podcast) 👥 560 📅 November 10, 2026 ⏱ 42 min 👁 0 📄 expert opinion 🧭 2026-11-10
Available in: English (current) Français

Keywords

GitHub Appprivate keyJWTsecurity researchsecret scanning

Summary

In this podcast episode, security researcher Gaetan Ferry discusses his recent investigation into publicly exposed private keys belonging to GitHub Apps. He explains that a GitHub App is a plugin-like tool installed on an organization, which authenticates to GitHub via a private RSA key that signs JWT tokens. The key is critical because a single compromised key can grant access to all organizations where the app is installed. To assess the scale of exposure, Ferry and his team filtered 500,000 leaked RSA keys from their dataset, selecting 5,000 candidates based on contextual indicators such as proximity to GitHub App identifiers. They then tested these keys against the GitHub API and found 474 validity, a striking 10% success rate compared to the typical 1-2% for other secrets. The compromised apps fell into two categories: marketplace apps with wide reach (one with over 330 installations, including large automotive companies) and internal tools with deep privileges (like BuildBuddy, whose leaked key could compromise its own servers). Approximately 10% of the valid keys held full administrative rights on their organizations. Disclosure efforts yielded mixed results: open-source maintainers were responsive, sometimes revoking keys within hours, while private companies were often non-responsive. A notable case involved a CDC app used as a bridge to their Azure infrastructure, which took two weeks and intervention from CISA to be revoked. Some applications were so abandoned that no contact could be established, and GitHub declined to revoke keys on request. The episode concludes with practical recommendations: organizations should inventory installed apps and prune unnecessary permissions, and developers should regularly rotate private keys since they never expire by default.

269 words

Critical Evaluation

Value of the Information & Strength of the Argument

The value of the information is high: the research provides concrete, quantified data on a significant security problem—leaked GitHub App private keys—with a 10% validity rate that highlights the severity. The argumentation is solid, grounded in a clear methodology: dataset filtering, contextual analysis, and API validation. The discussion includes real-world examples and impact assessments, which strengthens the credibility. The researcher also provides actionable advice for both organizations and developers. The argumentation is well-structured, moving from a technical explanation of GitHub Apps to the research process, findings, and mitigations, making it persuasive and educational for a technical audience.

Scientific Rigor, Source Quality, Title Accuracy

The scientific rigor is evident in the systematic approach: the dataset is defined, filtering criteria are explicit, and the validation process uses GitHub’s official API. The 474 valid keys are drawn from a large corpus, and the authors differentiate between app types and impact levels. Sources are not explicitly cited in the video, but the research appears to be an extension of prior work presented at NorthSec, which adds credibility. The title accurately mirrors the content, and the discussion is technically precise without oversimplification. No external references are provided in the description, which limits traceability, but the internal consistency and practical evidence support the reliability.

217 words

Title / Content Match

The title accurately reflects the technical focus on GitHub App private keys, though it omits the broader context of the research.

Quality & Reliability

8/10

Detailed technical discussion of a real security research study, with concrete statistics, examples, and a clear methodology. The researcher is directly involved in the work and provides practical recommendations.

Key Moments

Contribution & Novelties

The research quantifies a previously underappreciated risk: leaked GitHub App private keys have an unusually high validity rate (10%), amplifying the impact of a single exposure. It highlights the dual nature of such keys—enabling both broad compromise of many organizations and deep compromise of specific infrastructures—and reveals gaps in the disclosure and revocation processes, especially for abandoned applications. The findings underscore the need for better key rotation practices and careful permission scoping.

Pour aller plus loin :

  • GitHub Apps documentation — Official reference on how GitHub Apps work, including authentication and permissions.
  • JSON Web Token (JWT) — Technical background on the token format used for authentication with the private key.
  • GitHub Secret Scanning — Tool that can help detect exposed secrets, though it does not cover all cases of key leakage.
  • Public-key cryptography — Foundational concept behind the private key mechanism and its security implications.

145 words

Radar Profile

The profile shows high scores across the board, indicating a technically dense and reliable presentation. The balance between quantity and quality of information is nearly even, with a slight emphasis on technical depth, suggesting that the content is both informative and trustworthy for a cybersecurity audience.

Reliability 8/10