Skip to content
Fencer Intel
critical 9.8

CVE-2022-42968 json

Gitea vulnerable to Argument Injection

published 4y ago modified 2mo ago also BIT-gitea-2022-42968 , EUVD-2022-7173 , GHSA-w8xw-7crf-h23x , GO-2022-1065

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 73%
public exploits
0
none known

Summary

Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.

Patch / fix

  • go github.com/go-gitea/gitea 1.17.3
  • bitnami gitea 1.17.3
  • go code.gitea.io/gitea 1.17.3
  • gitea gitea 1.17.3
  • gitea Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 1.17.3-r0

alpine advisories ALPINE-CVE-2022-42968

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-42968 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-42968 updated cvss 9.8

gitea: Sanitize and Escape refs in git backend

  • Red Hat Logging Subsystem for Red Hat OpenShift openshift-logging/lokistack-gateway-rhel8 Red Hat OpenShift Serverless openshift-serverless-1/client-kn-rhel8 Red Hat Advanced Cluster Management for Kubernetes 2 acm-search-v2-operator-container Red Hat Advanced Cluster Security 3 advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-scanner-rhel8 Red Hat OpenShift GitOps openshift-gitops-kam, openshift-gitops-1/kam-delivery-rhel8 Red Hat Quay 3 quay/quay-builder-rhel8
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

1.43% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/go-gitea/gitea
<1.17.3
1.17.3
bitnami gitea
<1.17.3
1.17.3
go code.gitea.io/gitea
<1.17.3
1.17.3

Classification

Weakness
  • CWE-88 Improper Neutralization of Argument Delimiters in a Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.