dbcve.org
GiteaApplication

CVE-2021-45328

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-08
Fix available
A fix is available. Upgrade to 1.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.

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 · moderate confidence

Gitea before version 1.4.3 contains an open redirect vulnerability where internal URLs can be manipulated to redirect users to untrusted external sites. This occurs due to insufficient validation of redirect targets, allowing attackers to craft URLs that appear to point to internal resources but actually redirect to malicious external domains.

MitigationUpgrade Gitea to version 1.4.3 or later. As a temporary workaround, implement strict URL validation to ensure all redirects remain within the trusted domain and reject external URLs.

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
GiteaApplication
Affected:< 1.4.3

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Gitea version via web interface
    Log into your Gitea instance as an administrator and look at the footer of any page, or navigate to the Site Administration > Configuration page to view the version information.
    Affected if The displayed version number is less than 1.4.3 (for example, 1.4.2, 1.4.1, 1.4.0, or any 1.3.x release)
  2. Check Gitea version via command line
    Run 'gitea --version' on the server where Gitea is installed, or inspect the gitea binary file metadata.
    Affected if The command output or binary version is less than 1.4.3
  3. Check Gitea version from configuration or logs
    Examine the Gitea configuration file (app.ini) for version indicators, or check the startup logs for the version string.
    Affected if The configuration or logs indicate a version below 1.4.3
  4. Identify Gitea installation path and method
    Locate where Gitea is installed (for example, /usr/local/bin/gitea, /opt/gitea/, or a Docker container). Determine if it was installed via binary download, package manager, or Docker.
    Affected if The installed version cannot be determined or is confirmed to be prior to 1.4.3

You are affected if your Gitea installation version is any release before 1.4.3, as the open redirect vulnerability exists in those versions due to insufficient validation of redirect targets.

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 1.4.3 or later
Fixed in 1.4.3
Interim mitigation

Upgrade Gitea to version 1.4.3 or later. As a temporary workaround, implement strict URL validation to ensure all redirects remain within the trusted domain and reject external URLs.

Recommended fix High confidence

Gitea 1.4.3 or later

  1. Backup your Gitea data directory (by default /var/lib/gitea) and database
  2. Backup your Gitea configuration file (app.ini)
  3. Stop the Gitea service
  4. Download Gitea version 1.4.3 or later from the official releases (dl.gitea.io/gitea)
  5. Replace the existing Gitea binary with the new version
  6. Ensure file permissions are correct (executable by the Gitea user)
  7. Start the Gitea service
  8. Verify the upgrade was successful by checking the Gitea web interface and version number
Caveat Review release notes for any breaking changes between your current version and 1.4.3; standard practice is to test upgrades in a staging environment first

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

Fix this in Gitea Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-45328 — 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-45328 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