Bug 2155234 (CVE-2022-23536) - CVE-2022-23536 cortex: Alertmanager can expose local files content via specially crafted config
Summary: CVE-2022-23536 cortex: Alertmanager can expose local files content via specia...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2022-23536
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2155148
TreeView+ depends on / blocked
 
Reported: 2022-12-20 13:29 UTC by Avinash Hanwate
Modified: 2022-12-21 09:18 UTC (History)
22 users (show)

Fixed In Version: Cortex 1.13.2, Cortex 1.14.1
Clone Of:
Environment:
Last Closed: 2022-12-21 09:18:34 UTC
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2022-12-20 13:29:18 UTC
Cortex provides multi-tenant, long term storage for Prometheus. A local file inclusion vulnerability exists in Cortex versions 1.13.0, 1.13.1 and 1.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 Alertmanager service where `-experimental.alertmanager.enable-api` or `enable_api: true` is configured are affected. Affected Cortex users are advised to upgrade to patched versions 1.13.2 or 1.14.1. However as a workaround, Cortex administrators may reject Alertmanager configurations containing the `api_key_file` setting in the `opsgenie_configs` section before sending to the Set Alertmanager Configuration API.

https://cortexmetrics.io/docs/api/#set-alertmanager-configuration
https://github.com/cortexproject/cortex/security/advisories/GHSA-cq2g-pw6q-hf7j
https://github.com/cortexproject/cortex/releases/tag/v1.13.2
https://github.com/cortexproject/cortex/releases/tag/v1.14.1

Comment 3 Product Security DevOps Team 2022-12-21 09:18:31 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-23536


Note You need to log in before you can comment on or make changes to this bug.