CVE-2024-63956.3MediumCWE-200

CVE-2024-6395: GitHub Enterprise Server Information Disclosure Vulnerability Exposes Private Repository Names via Deploy Keys

GitHub · GitHub Enterprise Server

Affected: GitHub Enterprise Server · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days

42nd percentile

050100

Higher than 42% of scored CVEs

6.3MediumCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

An exposure of sensitive information vulnerability in GitHub Enterprise Server would allow an attacker to enumerate the names of private repositories that utilize deploy keys. This vulnerability did not allow unauthorized access to any repository content besides the name. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.17. This vulnerability was reported via the GitHub Bug Bounty program.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

GitHub · GitHub Enterprise Serverfrom 3.10.0 up to and including 3.10.13; from 3.11.0 up to and including 3.11.11; from 3.12.0 up to and including 3.12.5; from 3.13 up to and including 3.13.0; from 3.9.0 up to and including 3.9.16

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Information Exposure · Information Disclosure
Vendor: GitHub
Published: July 2024
Band: Unlikely (under 1%), July 2024
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2024-6395

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

View private repository NWO of deploy key via internal LFS APIGitHub · 2024 · medium severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2024-6395 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.