GitHub Enterprise Server susceptible to important auth bypass flaw

A important vulnerability affecting a number of variations of GitHub Enterprise Server might be exploited to bypass authentication and allow an attacker to realize administrator privileges on the machine.

The safety subject is recognized as CVE-2024-6800 and obtained a 9.5 severity ranking as per the CVSS 4.0 commonplace. It’s described as an XML signature wrapping downside that happens when utilizing the Safety Assertion Markup Language (SAML) authentication commonplace with sure identification suppliers.

“On GitHub Enterprise Server instances that use SAML single sign-on (SSO) authentication with specific IdPs utilizing publicly exposed signed federation metadata XML, an attacker could forge a SAML response to provision and/or gain access to a user account with site administrator privileges.” – GitHub

GitHub Enterprise Server (GHES) is a neighborhood model of GitHub for companies that lack the expertise for working with the general public cloud or wish to handle entry and safety controls.

In line with the FOFA search engine for community property uncovered on the general public internet, there are greater than 36,500 GHES cases accessible over the web, most of them (29,200) situated in the US.

Nevertheless, it’s unclear how lots of the uncovered GHES machines are working a susceptible model of the product.

Fofa scan results
Fofa scan outcomes for internet-exposed GHES cases
Supply: BleepingComputer

GitHub has addressed the problem in GHES variations 3.13.3, 3.12.8, 3.11.14, and 3.10.16.

The brand new GHES releases additionally embrace fixes for 2 different vulnerabilities, each with a medium severity rating:

  • CVE-2024-7711: permits points on public repositories to be modified by attackers
  • CVE-2024-6337: pertains to disclosing subject content material from a non-public repository

All three safety points have been reported by way of GitHub’s Bug Bounty program on the HackerOne platform.

GitHub warns that some companies may present errors through the configuration course of after making use of the safety updates however occasion ought to nonetheless begin accurately.

A number of points associated to log entries, reminiscence utilization, and repair interruptions throughout particular operations are additionally famous within the bulletin, so system admins are suggested to examine the ‘Known issues’ part earlier than they apply the replace.

Recent articles

INTERPOL Pushes for

Dec 18, 2024Ravie LakshmananCyber Fraud / Social engineering INTERPOL is...

Patch Alert: Essential Apache Struts Flaw Discovered, Exploitation Makes an attempt Detected

Dec 18, 2024Ravie LakshmananCyber Assault / Vulnerability Risk actors are...