Skip to content

← Public intelligence

Go package

github.com/brokercap/Bifrost

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.8GoPublished

    Bifrost vulnerable to authentication check flaw that leads to authentication bypass

    CVE-2022-39267 · GHSA-mxrx-fg8p-5p5j

    Affected
    • Go github.com/brokercap/Bifrost < 1.8.7-release
    Fixed in
    1.8.7-release· Vendor fix available
    Issue
    Impact The admin and monitor user groups need to be authenticated by username and password. If we delete the X-Requested-With: XMLHttpRequest field in the request header,the authentication will be bypassed. Patches https://github.com/brockercap/Bifrost/pull/201 Workarounds Upgrade to the latest version

    Recommended action: Upgrade to 1.8.7-release (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 8.5GoPublished

    Brokercap Bifrost subject to authentication bypass when using HTTP basic authentication

    CVE-2022-39219 · GHSA-p6fh-xc6r-g5hw

    Affected
    • Go github.com/brokercap/Bifrost <= 1.8.6-release
    Fixed in
    1.8.7-release· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.8.7-release (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →