CVE-2024-58166.9MediumCWE-863

CVE-2024-5816: Improper authorization allows persistent access in GitHub Enterprise Server

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

43rd percentile

050100

Higher than 43% of scored CVEs

6.9MediumCVSS 4.0

LowMediumHighCrit.

DescriptionCVE.org

An Incorrect Authorization vulnerability was identified in GitHub Enterprise Server that allowed a suspended GitHub App to retain access to the repository via a scoped user access token. This was only exploitable in public repositories while private repositories were not impacted. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in versions 3.9.17, 3.10.14, 3.11.12, 3.12.6, 3.13.1. 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: Incorrect Authorization · Access Control
Vendor: GitHub
Published: July 2024
Band: Unlikely (under 1%), July 2024
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2024-5816

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

GitHub Apps can access suspended installations via scoped user-to-server tokensGitHub · 2024 · medium severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2024-5816 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.