CVE-2017-18365

CVE-2017-18365 is a critical-severity vulnerability in Github with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 21% places it in the 97th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-502.

Key facts

Description

The Management Console in GitHub Enterprise 2.8.x before 2.8.7 has a deserialization issue that allows unauthenticated remote attackers to execute arbitrary code. This occurs because the enterprise session secret is always the same, and can be found in the product's source code. By sending a crafted cookie signed with this secret, one can call Marshal.load with arbitrary data, which is a problem because the Marshal data format allows Ruby objects.

Frequently asked questions

What is CVE-2017-18365?
The Management Console in GitHub Enterprise 2.8.x before 2.8.7 has a deserialization issue that allows unauthenticated remote attackers to execute arbitrary code. This occurs because the enterprise session secret is always the same, and can be found in the product's source code. By sending a crafted cookie signed with this secret, one can call Marshal.load with arbitrary data, which is a problem because the Marshal data format allows Ruby objects.
How severe is CVE-2017-18365?
CVE-2017-18365 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2017-18365 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 21% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-18365?
CVE-2017-18365 primarily affects Github. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-18365?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2017-18365 published?
CVE-2017-18365 was published on 2019-03-28 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Github

All CVEs affecting Github →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →