CVE-2024-1372Network attack vector

Admin SSH access via SAML command injection

Published Feb 13, 2024 · Updated May 9, 2025

Command injection in GitHub Enterprise Server before 3.12 allows remote authenticated users to gain administrative SSH access through SAML settings. GitHub identifies the vulnerable locus only as Management Console SAML configuration and has not published the specific input field or command-building operation. Exploitation requires network access to the instance and an editor-role Management Console account; successful injection grants administrative shell access to the appliance.

CVSS severity9.1
Critical
EPSS probability2.27%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Command injection in GitHub Enterprise Server before 3.12 allows remote authenticated users to gain administrative SSH access through SAML settings. GitHub identifies the vulnerable locus only as Management Console SAML configuration and has not published the specific input field or command-building operation. Exploitation requires network access to the instance and an editor-role Management Console account; successful injection grants administrative shell access to the appliance.

The record

CVE
CVE-2024-1372
Published
Feb 13, 2024
Updated
May 9, 2025
Vendor
Twitter
Product
GitHub Enterprise Server
Classifications
CWE-77, CWE-20, CAPEC-233, T1059
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 13, 2024CVE publishedPublication date reported by the CVE source.
  2. May 9, 2025Record 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.

  1. Affected versionversion=3.10.0 <3.10.7 changes=[{"at":"3.10.7","status":"unaffected"}]
  2. Affected versionversion=3.11.0 <3.11.5 changes=[{"at":"3.11.5","status":"unaffected"}]
  3. Affected versionversion=3.8.0 <3.8.15 changes=[{"at":"3.8.15","status":"unaffected"}]
  4. Affected versionversion=3.9.0 <3.9.10 changes=[{"at":"3.9.10","status":"unaffected"}]

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Twitter · GitHub Enterprise Serverversion=3.10.0 <3.10.7 changes=[{"at":"3.10.7","status":"unaffected"}]; version=3.11.0 <3.11.5 changes=[{"at":"3.11.5","status":"unaffected"}]; version=3.8.0 <3.8.15 changes=[{"at":"3.8.15","status":"unaffected"}]; version=3.9.0 <3.9.10 changes=[{"at":"3.9.10","status":"unaffected"}]

Published CVSS scores

9.1GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection')
CWE-20Improper Input Validation
CAPEC-233Privilege Escalation
T1059Command and Scripting Interpreter

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