Skip to content

← Public intelligence

Go package

github.com/prometheus/exporter-toolkit

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

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

  1. Medium, CVSS 6.2GoPublished

    Prometheus Exporter-Toolkit is vulnerable to authentication bypass

    CVE-2022-46146 · GHSA-7rg2-cxvp-9p7p

    Affected
    • Go github.com/prometheus/exporter-toolkit >= 0.8.0, < 0.8.2; < 0.7.2
    Fixed in
    0.8.20.7.2· Vendor fix available
    Issue
    Impact Prometheus and its exporters can be secured by a web.yml file that specifies usernames and hashed passwords for basic authentication. Passwords are hashed with bcrypt, which means that even if you have access to the hash, it is very hard to find the original password back. However, a flaw in the way this mechanism was implemented in the exporter toolkit makes it possible with people who know the hashed password to authenticate against Prometheus. A request can be forged by an attacker to poison the internal cache used to cache the computation of hashes and make subsequent requests successful. This cache is used in both happy and unhappy scenarios in order to limit side channel attacks that could tell an attacker if a user is present in the file or not. Patches The exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. Workarounds There is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication.…

    Recommended action: Upgrade to 0.8.2 or 0.7.2 by release line, 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 →