Elastic / X-Pack
9 CVEs
| CVE ID | Description | Severity | CVSS | Published |
|---|---|---|---|---|
| CVE-2018-3822 | X-Pack Security versions 6.2.0, 6.2.1, and 6.2.2 are vulnerable to a user impersonation attack via incorrect XML canonicalization and DOM traversal. An attacke… | CRITICAL | 9.8 | Mar 30, 2018 |
| CVE-2017-8448 | An error was found in the permission model used by X-Pack Alerting 5.0.0 to 5.6.0 whereby users mapped to certain built-in roles could create a watch that resu… | HIGH | 8.8 | Sep 28, 2017 |
| CVE-2017-8447 | An error was found in the X-Pack Security 5.3.0 to 5.5.2 privilege enforcement. If a user has either 'delete' or 'index' permissions on an index in a cluster,… | MEDIUM | 6.5 | Sep 28, 2017 |
| CVE-2017-8445 | An error was found in the X-Pack Security TLS trust manager for versions 5.0.0 to 5.5.1. If reloading the trust material fails the trust manager will be replac… | MEDIUM | 5.5 | Aug 18, 2017 |
| CVE-2017-8442 | Elasticsearch X-Pack Security versions 5.0.0 to 5.4.3, when enabled, can result in the Elasticsearch _nodes API leaking sensitive configuration information, su… | MEDIUM | 6.5 | Jul 7, 2017 |
| CVE-2017-8450 | X-Pack 5.1.1 did not properly apply document and field level security to multi-search and multi-get requests so users without access to a document and/or field… | HIGH | 7.5 | Jun 16, 2017 |
| 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 and exclude rules… | MEDIUM | 5.9 | Jun 16, 2017 |
| CVE-2017-8441 | 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… | MEDIUM | 4.3 | Jun 5, 2017 |
| CVE-2017-8438 | Elastic X-Pack Security versions 5.0.0 to 5.4.0 contain a privilege escalation bug in the run_as functionality. This bug prevents transitioning into the specif… | HIGH | 8.8 | Jun 5, 2017 |
Showing 1 to 9 of 9 CVEs