Patchfirst
CVE-2022-30781 Public exploit EPSS 87.9%

Gitea before 1.16.7 does not escape git fetch remote.

Summary

Gitea versions before 1.16.7 fail to properly escape the remote argument passed to the git fetch command, leaving the flaw in how the application handles git fetch remotes.

Heading is the official description · CVE.org
Breakdown
25.0 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15

Public exploit code (Metasploit) was available the same day.

  1. DisclosedPublic exploit codeMetasploitday 0

7 fixes in code.gitea.io/gitea over 17 months. The latest fix listed for code.gitea.io/gitea is 1.17.2.

Fixes in code.gitea.io/giteaGo package, by fixed version. Earlier and later fixes in the same package, not necessarily the same bug.

  1. 1.16.4CVE-2022-090510 Mar 2022
  2. 1.16.4CVE-2022-273133 May 2022
  3. 1.16.5CVE-2022-105824 Mar 2022
  4. 1.16.7CVE-2022-3078116 May 2022
  5. 1.16.9CVE-2022-192829 May 2022
  6. 1.16.9CVE-2022-3818312 Aug 2022
  7. 1.17.2CVE-2022-387957 Aug 2023Latest listed

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: code.gitea.io/gitea.

Gocode.gitea.io/giteaGHSA-p5f9-c9j9-g8qxGO-2022-0450

Upgrade to 1.26.3

Fixes this CVE and 2 other known vulnerabilities in this package (CVE-2020-14144, CVE-2026-20896).

Still affected on this line by CVE-2026-60004 (no fix published).

Gogo get code.gitea.io/gitea@v1.26.3

First fixed in 1.16.7 for CVE-2022-30781.

Affected versions

If you runUpgrade to
All versions before 1.16.71.26.3first fix for this CVE: 1.16.7

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

References

5 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close