Skip to content

Cortex's Alertmanager can expose local files content via specially crafted config

Moderate severity GitHub Reviewed Published Dec 19, 2022 in cortexproject/cortex • Updated Oct 2, 2023

Package

gomod github.com/cortexproject/cortex (Go)

Affected versions

= 1.14.0
>= 1.13.0, < 1.13.2

Patched versions

1.14.1
1.13.2

Description

Impact

A local file inclusion vulnerability exists in Cortex versions v1.13.0, v1.13.1 and v1.14.0, where a malicious actor could remotely read local files as a result of parsing maliciously crafted Alertmanager configurations when submitted to the Alertmanager Set Configuration API. Only users of the Cortex Alertmanager service using -experimental.alertmanager.enable-api or enable_api: true are affected.

Specific Go Packages Affected

github.com/cortexproject/cortex/pkg/alertmanager

Patches

Affected Cortex users are advised to upgrade to versions 1.13.2 or 1.14.1.

Workarounds

Patching is ultimately advised. Using out-of-bound validation, Cortex administrators may reject Alertmanager configurations containing the api_key_file setting in the opsgenie_configs section and opsgenie_api_key_file in the global section before sending to the Set Alertmanager Configuration API as a workaround.

References

For more information

If you have any questions or comments about this advisory:

References

@alanprot alanprot published to cortexproject/cortex Dec 19, 2022
Published to the GitHub Advisory Database Dec 19, 2022
Reviewed Dec 19, 2022
Published by the National Vulnerability Database Dec 19, 2022
Last updated Oct 2, 2023

Severity

Moderate

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
Low
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:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.112%
(46th percentile)

Weaknesses

CVE ID

CVE-2022-23536

GHSA ID

GHSA-cq2g-pw6q-hf7j

Source code

Credits

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