github.com/prometheus/exporter-toolkit
Utility package to build exporters
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 32
- Cadence
- ~43 days
- Last 12 months
- 7
Reach
- Stars
- 309
Details
- First release
- Dec 10, 2020
| Version | Released | |
|---|---|---|
v0.19.0
minor
|
v0.19.0
minor
Dependencies (8)
|
|
v0.18.0
minor
|
v0.18.0
minor
Dependencies (8)
|
|
v0.17.1
patch
|
v0.17.1
patch
Dependencies (8)
|
|
v0.17.0
minor
|
v0.17.0
minor
Dependencies (8)
|
|
v0.16.0
minor
|
v0.16.0
minor
Dependencies (8)
|
|
v0.15.1
patch
|
v0.15.1
patch
Dependencies (8)
|
|
v0.15.0
minor
|
v0.15.0
minor
Dependencies (8)
|
|
v0.14.1
patch
|
v0.14.1
patch
Dependencies (7)
|
|
v0.14.0
minor
|
v0.14.0
minor
Dependencies (7)
|
|
v0.13.2
patch
|
v0.13.2
patch
Dependencies (7)
|
|
v0.13.1
patch
|
v0.13.1
patch
Dependencies (7)
|
|
v0.13.0
minor
|
v0.13.0
minor
Dependencies (7)
|
|
v0.12.0
minor
|
v0.12.0
minor
Dependencies (8)
|
|
v0.11.0
minor
|
v0.11.0
minor
Dependencies (7)
|
|
v0.10.0
minor
|
v0.10.0
minor
Dependencies (7)
|
|
v0.9.1
patch
|
v0.9.1
patch
Dependencies (7)
|
|
v0.9.0
minor
|
v0.9.0
minor
Dependencies (7)
|
|
v0.7.3
patch
|
v0.7.3
patch
Dependencies (6)
|
|
v0.7.2
patch
|
v0.7.2
patch
Dependencies (6)
|
|
v0.8.2
patch
|
v0.8.2
patch
Dependencies (7)
|
|
v0.8.1
patch
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.8.1
patch
Dependencies (7)
|
|
v0.8.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.8.0
minor
Dependencies (7)
|
|
v0.7.1
patch
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.7.1
patch
Dependencies (6)
|
|
v0.7.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.7.0
minor
Dependencies (6)
|
|
v0.6.1
patch
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.6.1
patch
Dependencies (6)
|
|
v0.6.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.6.0
minor
Dependencies (6)
|
|
v0.5.1
patch
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.5.1
patch
Dependencies (6)
|
|
v0.5.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.5.0
minor
Dependencies (6)
|
|
v0.4.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.4.0
minor
Dependencies (6)
|
|
v0.3.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.3.0
minor
Dependencies (6)
|
|
v0.2.0
minor
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.2.0
minor
Dependencies (6)
|
|
v0.1.0
initial
1 CVE
CVE-2022-46146
GHSA-7rg2-cxvp-9p7p
GO-2022-1130
Dec 02, 2022
Prometheus Exporter-Toolkit is vulnerable to authentication bypass
6.2
/ 10
Medium
Local
Low
None
None
Unchanged
High
None
None
ImpactPrometheus 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. PatchesThe exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. WorkaroundsThere is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication. CreditWe want to thank Lei Wan reporting this security issue. Fixed in
0.7.2
0.8.2
References
Updated Sep 10, 2026 · Source: OSV.dev |
v0.1.0
initial
Dependencies (5)
|