CVE-2022-38795 json
Gitea erroneous repo clones
published 3y ago modified 2mo ago also BIT-gitea-2022-38795 , EUVD-2023-2246 , GHSA-8j3v-68w3-3848 , GO-2023-1999
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
In Gitea through 1.17.1, repo cloning can occur in the migration function.
Patch / fix
- go code.gitea.io/gitea 1.17.2
- bitnami gitea 1.17.2
- github.com/go-gitea/gitea#20869 pull request
- github.com/go-gitea/gitea#20892 pull request
Is CVE-2022-38795 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | code.gitea.io/gitea | <1.17.2 |
1.17.2 |
| bitnami | gitea | <1.17.2 |
1.17.2 |
References
-
github.com
/go-gitea/gitea/pull/20869
web, patch, vendor-advisory, advisory
-
github.com
/go-gitea/gitea/pull/20892
web, patch, vendor-advisory, advisory
-
blog.gitea.com
/release-of-1.17.2/
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2022-38795
advisory, web
-
blog.gitea.com
/release-of-1.17.2
web
-
github.com
/go-gitea/gitea
package
-
github.com
/advisories/GHSA-8j3v-68w3-3848
advisory
Sources
- CVE List CVE-2022-38795
- GitHub Advisory GHSA-8j3v-68w3-3848
- NVD CVE-2022-38795
- OSV BIT-gitea-2022-38795
- OSV GO-2023-1999
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.