# CVE-2022-39205: Access Control Bypass in Onedev

> Unauthenticated attackers can bypass access controls to execute arbitrary code on Onedev instances lacking proper reverse proxy configuration.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **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-4f9h-h82c-4xm2

## What is CVE-2022-39205?

CVE-2022-39205 is a critical authentication bypass 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. In versions of Onedev prior to 7.3.0 unauthenticated users can take over a OneDev instance if there is no properly configured reverse proxy. The /git-prereceive-callback endpoint is used by the pre-receive git hook on the server to check for branch protections during a push event. It is only intended to be accessed from localhost, but the check relies on the X-Forwarded-For header. Invoking this endpoint leads to the execution of one of various git commands. The environment variables of this command execution can be controlled via query parameters. This allows attackers to write to arbitrary files, which can in turn lead to the execution of arbitrary code. Such an attack would be very hard to detect, which increases the potential impact even more. Users are advised to upgrade. There are no known workarounds for this issue.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Onedev Project Onedev.

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

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

## Is CVE-2022-39205 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39205 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-39205 and fix it if it is affected.

What it is: CVE-2022-39205 is a critical authentication bypass 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-39205 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-39205/ (Markdown: https://insights.sbomify.com/CVE-2022-39205/index.md)
```

## Sources

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

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