Elastic X-Pack Security versions prior to 5.4.1 and 5.3.3 did not always correctly apply Document Level Security to index aliases. This bug could allow a user with restricted permissions to view data they should not have access to when performing certain operations against an index alias.
Weakness
While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| X-pack |
Elastic |
5.3.0 (including) |
5.3.3 (excluding) |
| X-pack |
Elastic |
5.4.0 (including) |
5.4.1 (excluding) |
Potential Mitigations
- Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
- Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References