Skip to content

Gogs allows argument Injection when tagging new releases

High severity GitHub Reviewed Published Dec 23, 2024 in gogs/gogs • Updated Dec 23, 2024

Package

gomod gogs.io/gogs (Go)

Affected versions

<= 0.13.0

Patched versions

0.13.1

Description

Impact

Unprivileged user accounts with at least one SSH key can read arbitrary files on the system. For instance, they could leak the configuration files that could contain database credentials ([database] *) and [security] SECRET_KEY. Attackers could also exfiltrate TLS certificates, other users' repositories, and the Gogs database when the SQLite driver is enabled.

Patches

Unintended Git options has been ignored for creating tags (gogs/gogs#7872). Users should upgrade to 0.13.1 or the latest 0.14.0+dev.

Workarounds

No viable workaround available, please only grant access to trusted users to your Gogs instance on affected versions.

References

https://www.cve.org/CVERecord?id=CVE-2024-39933

References

@unknwon unknwon published to gogs/gogs Dec 23, 2024
Published to the GitHub Advisory Database Dec 23, 2024
Reviewed Dec 23, 2024
Last updated Dec 23, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:L/S:C/UI:N

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-39933

GHSA ID

GHSA-m27m-h5gj-wwmg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.