Monday, February 10, 2025
HomeCVE/vulnerabilityGogs Vulnerabilities Let Attackers Hack Instances & Steal Source Code

Gogs Vulnerabilities Let Attackers Hack Instances & Steal Source Code

Published on

SIEM as a Service

Follow Us on Google News

Gogs is a standard open-source code hosting system used by many developers.

Several Gogs vulnerabilities have been discovered recently by the cybersecurity researchers at SonarSource. 

Gogs can be hacked through these flaws, which put its instances at risk of source code theft, backdoor implantation as well as code removal.

Gogs Vulnerabilities

Despite Gogs’ widespread use, with more than 44,000 GitHub stars and 90 million Docker image downloads, these vulnerabilities remain unpatched.

This finding highlights the need to secure development tools and self-hosted code repositories.

"Is Your System Under Attack? Try Cynet XDR: Automated Detection & Response for Endpoints, Networks, & Users!"- Free Demo

The Gogs’ built-in SSH server contains an Argument Injection Vulnerability that allows authenticated attackers to execute any command on the server.

The vulnerability exploits the ‘–split-string‘ option in the ‘env’ command to bypass security measures.

As a result, this vulnerability continues to be unpatched even in the latest Gogs release (0.13.0).

This security issue is consequently exposed in about 7,300 open Gogs instances on Shodan that largely endangers source code integrity and server protection for several organizations using Gogs for code hosting, reads SonarSource report.

Shodan report (Source – Sonar)

In order to exploit the Gogs SSH server vulnerability, three conditions must be met:- 

  • The built-in SSH server needs to be switched on.
  • There is a necessity for an authentic SSH key.
  • The use of “env -–split-string” compatible version.

Exploitable set-ups typically employ GNU core-utils in Ubuntu or Debian, while Alpine Linux-based Docker images and Windows installations are not affected.

If registration is enabled, attackers can easily create accounts and add SSH keys. Admins can confirm this vulnerability by checking their SSH settings in the admin panel and look if ‘env –help’ shows ‘–split-string’ among its options.

Gogs maintainers ceased communication after initially accepting vulnerability reports, leaving all four reported issues unpatched in the latest version. 

As a result, users must implement their own mitigations to protect their installations.

Recommendations

Here below we have mentioned all the recommendations and mitigations provided by the security analysts:-

  • Disable the built-in SSH server
  • Disable user registration
  • Switch to Gitea
  • Argument Injection in the built-in SSH server
  • Argument Injection when tagging new releases

Are you from SOC/DFIR Teams? - Sign up for a free ANY.RUN account! to Analyse Advanced Malware Files

Tushar Subhra
Tushar Subhra
Tushar is a Cyber security content editor with a passion for creating captivating and informative content. With years of experience under his belt in Cyber Security, he is covering Cyber Security News, technology and other news.

Latest articles

Hackers Exploit AnyDesk Vulnerability to Gain Admin Access – PoC Released

A newly discovered vulnerability in AnyDesk, the popular remote desktop software, has sparked serious...

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Hackers Exploit AnyDesk Vulnerability to Gain Admin Access – PoC Released

A newly discovered vulnerability in AnyDesk, the popular remote desktop software, has sparked serious...

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...