Editor-level SSH access via storage command injection
Published Apr 19, 2024 · Updated Aug 1, 2024
Command injection in storage settings in GitHub Enterprise Server allows remote authenticated users to gain SSH access to the appliance. Management Console storage configuration incorporates crafted input into a command without neutralizing argument delimiters. Exploitation requires instance access and an editor-role Management Console account, after which injected commands obtain appliance SSH access.
Summary
What happened
Command injection in storage settings in GitHub Enterprise Server allows remote authenticated users to gain SSH access to the appliance. Management Console storage configuration incorporates crafted input into a command without neutralizing argument delimiters. Exploitation requires instance access and an editor-role Management Console account, after which injected commands obtain appliance SSH access.
The record
- CVE
- CVE-2024-3684
- Published
- Apr 19, 2024
- Updated
- Aug 1, 2024
- Vendor
- Product
- GitHub Enterprise Server
- Classifications
- CWE-88, CAPEC-1, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.10.0 <3.10.10
- Affected versionversion=3.11.0 <3.11.8
- Affected versionversion=3.12.0 <3.12.2
- Affected versionversion=3.9.0
- Affected versionversion=3.9.0 <3.9.13
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo