dbcve.org
GogsApplication

CVE-2021-32546

HIGH · 8.8 CVSS v3.1 Published 2022-06-02
Fix available
A fix is available. Upgrade to 0.12.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Missing input validation in internal/db/repo_editor.go in Gogs before 0.12.8 allows an attacker to execute code remotely. An unprivileged attacker (registered user) can overwrite the Git configuration in his repository. This leads to Remote Command Execution, because that configuration can contain an option such as sshCommand, which is executed when a master branch is a remote branch (using an ssh:// URI). The remote branch can also be configured by editing the Git configuration file. One can create a new file in a new repository, using the GUI, with "\" as its name, and then rename this file to .git/config with the custom configuration content (and then save it).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Missing input validation in Gogs' repo_editor.go allows unprivileged registered users to create files with arbitrary names, including overwriting .git/config. By injecting sshCommand configuration options, attackers achieve remote command execution when the master branch uses an ssh:// URI.

MitigationUpgrade Gogs to version 0.12.8 or later which includes input validation fixes. If immediate upgrade is not possible, disable ssh:// repository URL support or implement additional access controls on file creation APIs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GogsApplication
Affected:< 0.12.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Gogs version
    Run `gogs --version` or check the admin dashboard under 'Administration > System Settings' to see the currently installed version
    Affected if Version is below 0.12.8
  2. Verify user registration status
    Go to Administration > Authentication > Authentication Sources, or inspect the [service] section in conf/app.ini for `DISABLE_REGISTRATION` or `ENABLE_REGISTRATION` setting
    Affected if User registration is enabled (DISABLE_REGISTRATION=false or ENABLE_REGISTRATION=true)
  3. Check for ssh:// repository URLs
    Inspect repository settings in the web UI or check .git/config files in repository directories for remote URLs starting with ssh://
    Affected if Any repository uses an ssh:// remote URL (as opposed to http://, https://, or git://)
  4. Inspect .git/config for sshCommand injection
    Examine .git/config files in repositories, particularly looking for a `[core] sshCommand` section with potentially malicious commands
    Affected if Any .git/config contains unexpected or suspicious sshCommand entries that were not added by administrators

Environment is affected if Gogs version is below 0.12.8, user registration is enabled, and ssh:// repository URLs are in use, allowing unprivileged users to potentially inject malicious sshCommand entries via file creation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.12.8 or later
Fixed in 0.12.8
Interim mitigation

Upgrade Gogs to version 0.12.8 or later which includes input validation fixes. If immediate upgrade is not possible, disable ssh:// repository URL support or implement additional access controls on file creation APIs.

Recommended fix High confidence

Gogs 0.12.8

  1. Backup your Gogs data and database before upgrading
  2. Download Gogs version 0.12.8 or later from the official repository (https://github.com/gogs/gogs/releases)
  3. Stop the Gogs service
  4. Replace the existing Gogs binary with the new version
  5. Review release notes for any required migration steps
  6. Start the Gogs service
  7. Verify the upgrade was successful by checking the admin dashboard

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gogs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32546 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data