# CVE-2022-39219: Bifrost users using basic authntication can bypass write permission limit

> Attackers with read-only access can bypass write permission limits in Bifrost when using HTTP basic authentication, allowing unauthorized data modification.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-p6fh-xc6r-g5hw, GO-2022-1023

## What is CVE-2022-39219?

CVE-2022-39219 is a high-severity authentication bypass vulnerability in brokercap Bifrost, published on 26 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Bifrost is a middleware package which can synchronize MySQL/MariaDB binlog data to other types of databases. Versions 1.8.6-release and prior are vulnerable to authentication bypass when using HTTP basic authentication. This may allow group members who only have read permissions to write requests when they are normally forbidden from doing so. Version 1.8.7-release contains a patch. There are currently no known workarounds.

Weakness: CWE-287 (Improper Authentication)

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

3 open source packages ship an affected version, including github.com/brokercap/Bifrost. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/brokercap/Bifrost` | Go | All versions | 1.8.7-release |
| `github.com/brokercap/Bifrost` | Go | All versions | 1.8.7-release |
| `github.com/brokercap/Bifrost` | Go | All versions | 1.8.7-release |

Products: Xbifrost Bifrost.

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

Upgrade github.com/brokercap/Bifrost to 1.8.7-release or later.

## Is CVE-2022-39219 being exploited?

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

## Other vulnerabilities in brokercap Bifrost

- [CVE-2022-39267](https://insights.sbomify.com/CVE-2022-39267/): Brokercap Bifrost vulnerable to authentication bypass for admin and monitor user groups (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39219 is a high-severity authentication bypass vulnerability in brokercap Bifrost, published on 26 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39219 exists.

Affected packages and fixed versions:
- github.com/brokercap/Bifrost (Go): affected all versions; fixed in 1.8.7-release
- github.com/brokercap/Bifrost (Go): affected all versions; fixed in 1.8.7-release
- github.com/brokercap/Bifrost (Go): affected all versions; fixed in 1.8.7-release

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-39219/ (Markdown: https://insights.sbomify.com/CVE-2022-39219/index.md)
```

## Sources

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

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