# CVE-2022-39267: Brokercap Bifrost vulnerable to authentication bypass for admin and monitor user groups

> Attackers can bypass authentication for admin and monitor groups by removing a specific HTTP header, gaining unauthorized access to the Bifrost middleware.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 19 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-mxrx-fg8p-5p5j, GO-2022-1067

## What is CVE-2022-39267?

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

### Official description

Bifrost is a heterogeneous middleware that synchronizes MySQL, MariaDB to Redis, MongoDB, ClickHouse, MySQL and other services for production environments. Versions prior to 1.8.8-release are subject to authentication bypass in the admin and monitor user groups by deleting the X-Requested-With: XMLHttpRequest field in the request header. This issue has been patched in 1.8.8-release. There are no known workarounds.

Weakness: CWE-287 (Improper Authentication)

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

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-39267?

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

## Is CVE-2022-39267 being exploited?

There is no known exploitation of CVE-2022-39267 in the wild and no public exploit code.

## Other vulnerabilities in brokercap Bifrost

- [CVE-2022-39219](https://insights.sbomify.com/CVE-2022-39219/): Bifrost users using basic authntication can bypass write permission limit (high 8.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39267 is a high-severity authentication bypass vulnerability in brokercap Bifrost, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-39267 in the wild and no public exploit code.

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

## Sources

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

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