# CVE-2022-39208: Git Repository Disclosure in Onedev

> Unauthenticated attackers can read all project files and build artifacts from the Onedev Git server directory, leading to significant data leakage.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-h427-rv56-c9h2

## What is CVE-2022-39208?

CVE-2022-39208 is a high-severity vulnerability in theonedev onedev, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2022-39208?

It affects 1 product.


Products: Onedev Project Onedev.

## How do I fix CVE-2022-39208?

No fix has been published for CVE-2022-39208 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-39208 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39208 exists.

## Other vulnerabilities in theonedev onedev

- [CVE-2021-21242](https://insights.sbomify.com/CVE-2021-21242/): Pre-Auth Unsafe Deserialization on AttachmentUploadServet (critical 10.0)
- [CVE-2021-21243](https://insights.sbomify.com/CVE-2021-21243/): Pre-Auth Unsafe Deserialization on KubernetesResource (critical 10.0)
- [CVE-2021-21244](https://insights.sbomify.com/CVE-2021-21244/): Pre-Auth SSTI via Bean validation message tampering (critical 10.0)
- [CVE-2021-21245](https://insights.sbomify.com/CVE-2021-21245/): Pre-Auth Arbitrary File Upload (critical 10.0)
- [CVE-2022-39206](https://insights.sbomify.com/CVE-2022-39206/): CI/CD Docker Escape in OneDev (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39208 and fix it if it is affected.

What it is: CVE-2022-39208 is a high-severity vulnerability in theonedev onedev, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39208 exists.

Affected product: theonedev onedev. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39208/ (Markdown: https://insights.sbomify.com/CVE-2022-39208/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39208
- OSV: https://osv.dev/vulnerability/CVE-2022-39208

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39208/
Summaries are generated and may contain mistakes; the official description above is the record.