Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Safely handling user input in Elasticsearch documents #58040

Open
kobelb opened this issue Feb 19, 2020 · 1 comment
Open

Safely handling user input in Elasticsearch documents #58040

kobelb opened this issue Feb 19, 2020 · 1 comment
Labels
Feature:Hardening Harding of Kibana from a security perspective R&D Research and development ticket (not meant to produce code, but to make a decision) Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@kobelb
Copy link
Contributor

kobelb commented Feb 19, 2020 •
edited
Loading

Elasticsearch documents can commonly contain data that is specified by end-users, and shouldn't be trusted. We should figure out how to safely handle these documents without exposing ourselves to the general pitfalls that come along with unconstrained user input.
@kobelb kobelb added Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! Feature:Hardening Harding of Kibana from a security perspective labels Feb 19, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego legrego added the R&D Research and development ticket (not meant to produce code, but to make a decision) label Mar 25, 2020
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Aug 5, 2021
@legrego legrego mentioned this issue Aug 31, 2021
Merged
@jportner jportner mentioned this issue Aug 31, 2021
Closed
@legrego legrego removed EnableJiraSync loe:small Small Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Hardening Harding of Kibana from a security perspective R&D Research and development ticket (not meant to produce code, but to make a decision) Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@watson @kobelb @legrego @elasticmachine