Home

Description

In Search Guard FLX versions 3.1.1 and earlier, Field-Level Security (FLS) rules are improperly enforced on object-valued fields. When an FLS exclusion rule (e.g., ~field) is applied to a field which contains an object as its value, the object is correctly removed from the _source returned by search operations. However, the object members (i.e., child attributes) remain accessible to search queries. This exposure allows adversaries to infer or reconstruct the original contents of the excluded object. Workaround - If you cannot upgrade immediately and FLS exclusion rules are used for object valued attributes (like ~object), add an additional exclusion rule for the members of the object (like ~object.*).

PUBLISHED Reserved 2025-10-24 | Published 2025-10-29 | Updated 2025-10-29 | Assigner floragunn




MEDIUM: 6.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Problem types

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

CWE-732 Incorrect Permission Assignment for Critical Resource

Product status

Default status
unaffected

1.0.0 (semver)
affected

References

search-guard.com/cve-advisory/

docs.search-guard.com/latest/changelog-searchguard-flx-3_1_2

cve.org (CVE-2025-12147)

nvd.nist.gov (CVE-2025-12147)

Download JSON