CVE-2022-39208 json
Git Repository Disclosure in Onedev
published 2022-09-13 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-41747
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Onedev is an open source, self-hosted Git Server with CI/CD and Kanban. All files in the /opt/onedev/sites/ directory are exposed and can be read by unauthenticated users. This directory contains all projects, including their bare git repos and build artifacts. This file disclosure vulnerability can be used by unauthenticated attackers to leak all project files of any project. Since project IDs are incremental, an attacker could iterate through them and leak all project data. This issue has been resolved in version 7.3.0 and users are advised to upgrade. There are no known workarounds for this issue.
Patch / fix
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.93% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- blog.sonarsource.com https://blog.sonarsource.com/onedev-remote-code-execution/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- theonedev onedev
Classification
- Weakness
-
- CWE-552 Files or Directories Accessible to External Parties
References
-
github.com
/theonedev/onedev/commit/8aa94e0daf8447cdf76d4f27bfda0a85a7ea5822
patch, third-party-advisory
-
blog.sonarsource.com
/onedev-remote-code-execution/
exploit, third-party-advisory
-
github.com
/theonedev/onedev/security/advisories/GHSA-h427-rv56-c9h2
third-party-advisory
Sources
- CVE List CVE-2022-39208
- NVD CVE-2022-39208
Fencer Vulns 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.