Enterprise Server: Improper Control of Generation of Code
CVE-2025-3509 is a high-severity improper control of generation of code vulnerability in Enterprise Server from GitHub, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists version 13.17.1 as the first without the flaw, so updating Enterprise Server to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.31% chance of exploitation within 30 days, higher than 71% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Enterprise Server to 13.17.1 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| GitHub | Enterprise Server | 3.13.0 through 3.13.15; 3.14.0 through 3.14.12; 3.15.0 through 3.15.7; 3.16.0 through 3.16.3; 13.17.0 up to, but not including, 13.17.1 | 13.17.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.1 | High | CNA (github.com) |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
A Remote Code Execution (RCE) vulnerability was identified in GitHub Enterprise Server that allowed attackers to execute arbitrary code by exploiting the pre-receive hook functionality, potentially leading to privilege escalation and system compromise. The vulnerability involves using dynamically allocated ports that become temporarily available, such as during a hot patch upgrade. This means the vulnerability is only exploitable during specific operational conditions, which limits the attack window. Exploitation required either site administrator permissions to enable and configure pre-receive hooks or a user with permissions to modify repositories containing pre-receive hooks where this functionality was already enabled. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.18 and was fixed in versions 3.17.1, 3.16.4, 3.15.8, 3.14.13, 3.13.16. This vulnerability was reported via the GitHub Bug Bounty program.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- docs.github.com/en/[email protected]/admin/release-notes#3.13.16Release Notes
- docs.github.com/en/[email protected]/admin/release-notes#3.14.13Release Notes
- docs.github.com/en/[email protected]/admin/release-notes#3.15.8Release Notes
- docs.github.com/en/[email protected]/admin/release-notes#3.16.4Release Notes
- docs.github.com/en/[email protected]/admin/release-notes#3.17.1Release Notes
Other vulnerabilities in Enterprise Server
- 7.7 High severity
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.5 High severity
- 7.4 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 7.3 High severity
- 9.9 Critical severity
- 9.8 Critical severity
- 9.1 Critical severity
Spotted an error? Tell us.