CVE-2024-5566: Improper Privilege Management allows for access to unauthorized repository content during migration
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: GitHub GitHub Enterprise Server 3.10.14, 3.11.12, 3.12.6.
Low priority for now. Upgrade to GitHub GitHub Enterprise Server 3.10.14, 3.11.12, 3.12.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An improper privilege management vulnerability allowed users to migrate private repositories without having appropriate scopes defined on the related Personal Access Token. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.14 and was fixed in version 3.13.1, 3.12.6, 3.11.12, 3.10.14, and 3.9.17.
- Published
- Jul 16, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-269
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.5
- CNA · GitHub_P
- 5.8
- 0.7 point gap
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| github | enterprise server | cpe:2.3:a:github:enterprise_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- github enterprise server3.9.0 and later · before 3.9.17
- github enterprise server3.10.0 and later · before 3.10.14
- github enterprise server3.11.0 and later · before 3.11.12
- github enterprise server3.12.0 and later · before 3.12.6
- github enterprise server3.13.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_P). Independent of NVD's CPE analysis and usually ahead of it.
GitHub GitHub Enterprise Server
- 3.9.0 and later · up to and including 3.9.16affected · semverfixed in 3.9.17
- 3.10.0 and later · up to and including 3.10.13affected · semverfixed in 3.10.14
- 3.11.0 and later · up to and including 3.11.11affected · semverfixed in 3.11.12
- 3.12.0 and later · up to and including 3.12.5affected · semverfixed in 3.12.6
- 3.13 and later · up to and including 3.13.0affected · semverfixed in 3.13.1
Same product
github: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-0200Unsafe Reflection in Github Enterprise Server leading to Command Injection61This week
- CVE-2024-0507Privilege Escalation by Code Injection in the Management Console in GitHub Enterprise Server55Plan
- CVE-2026-3854Remote code execution via git push option injection in GitHub Enterprise Server46Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-4985May 20, 2024 · An authentication bypass vulnerability was present in the GitHub Enterprise Server (GHES) when utilizing SAML single sign-on authentication 41Plan
- ← EarlierCVE-2024-5746Jun 20, 2024 · A Server-Side Request Forgery vulnerability was identified in GitHub Enterprise Server that allowed an attacker with the Site Administrator 28Monitor
- Later →CVE-2024-5795Jul 16, 2024 · Denial of Service vulnerability was identified in GitHub Enterprise Server that allowed resource exhaustion26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| GitHub GitHub Enterprise Server | 3.10.14 | Vendor (CNA) |
| GitHub GitHub Enterprise Server | 3.11.12 | Vendor (CNA) |
| GitHub GitHub Enterprise Server | 3.12.6 | Vendor (CNA) |
| GitHub GitHub Enterprise Server | 3.13.1 | Vendor (CNA) |
| GitHub GitHub Enterprise Server | 3.9.17 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Ganesh Kumar (iamgk808)finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-46647208 days apartImproper Privilege Management in GitHub Enterprise Server management console leads to privilege escalation35Monitor
- CVE-2024-8810114 days apartPrivilege Management vulnerability was identified in GitHub Enterprise Server that allowed GitHub Apps to grant themselves write access34Monitor
- CVE-2024-347088 days apartRepository administrator can bypass organization's ruleset using deploy keys28Monitor
- CVE-2024-1908118 days apartImproper Privilege Management vulnerability was identified in GitHub Enterprise Server that allowed Privilege Escalation26Monitor
- CVE-2024-826369 days apartAn improper privilege management vulnerability allowed arbitrary workflows to be committed using an improperly scoped PAT through the use of24Monitor
- CVE-2023-6804208 days apartImproper Privilege Management allows for arbitrary workflows to be run22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.