Skip to content

Unauthenticated Miniflux user can bypass allowed networks check to obtain Prometheus metrics

High severity GitHub Reviewed Published Mar 17, 2023 in miniflux/v2 • Updated Apr 2, 2025

Package

gomod miniflux.app (Go)

Affected versions

<= 1.0.46

Patched versions

None
gomod miniflux.app/v2 (Go)
<= 2.0.42
2.0.43

Description

Impact

An unauthenticated user can retrieve Prometheus metrics from a publicly reachable Miniflux instance where the METRICS_COLLECTOR configuration option is enabled and METRICS_ALLOWED_NETWORKS is set to 127.0.0.1/8 (the default).

Patches

PR #1745 fixes the problem. Available in Miniflux >= 2.0.43.

Workarounds

Set METRICS_COLLECTOR to false (default) or run Miniflux behind a trusted reverse-proxy.

References

References

@fguillot fguillot published to miniflux/v2 Mar 17, 2023
Published by the National Vulnerability Database Mar 17, 2023
Published to the GitHub Advisory Database Apr 2, 2025
Reviewed Apr 2, 2025
Last updated Apr 2, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(59th percentile)

Weaknesses

CVE ID

CVE-2023-27591

GHSA ID

GHSA-3qjf-qh38-x73v

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.