Gogs Path Traversal Vulnerability: Potential Remote Code Execution
An early warning has been issued regarding a path traversal vulnerability in Gogs that could potentially lead to remote code execution through Git hooks. Users of Gogs are advised to upgrade to the latest version and avoid using organization names with path traversal sequences.
What happened
Gogs, a self-hosted Git service, reportedly has a path traversal vulnerability in organization names (tracked as GHSA-C39W-43GM-34H5). This vulnerability appears to allow storing and retrieving data at arbitrary locations on the filesystem, potentially leading to remote code execution through Git hooks. The vulnerability is said to affect versions of Gogs introduced at version 0 and is fixed in version 0.14.3. It is under investigation and users are recommended to upgrade to the latest version of Gogs and avoid using organization names with path traversal sequences to mitigate potential risks. For more detailed information, consult the primary sources.
How 0Day mitigates this
gogs is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.