X-Pack vulnerabilitiesRanked by how likely they are to be used.
X-Pack is made by Elastic. We track 9 published vulnerabilities in it, across 52 versions. None of them is on the list of flaws known to be exploited today. If you run X-Pack, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which X-Pack vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of X-Pack's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which X-Pack flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.6%CVE-2018-3822Critical
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.
- 1.0%CVE-2017-8438High
Elastic X-Pack Security versions 5.0.0 to 5.4.0 contain a privilege escalation bug in the run_as functionality.
- 0.9%CVE-2017-8442Medium
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, such as the paths and passphrases of SSL keys that were...
- 0.9%CVE-2017-8450High
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 may have been able to access this information.
- 0.9%CVE-2017-8448High
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 results in that user gaining elevated privileges.
- 0.8%CVE-2017-8449Medium
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...
- 0.7%CVE-2017-8441Medium
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.
- 0.6%CVE-2017-8447Medium
An error was found in the X-Pack Security 5.3.0 to 5.5.2 privilege enforcement.
- 0.2%CVE-2017-8445Medium
An error was found in the X-Pack Security TLS trust manager for versions 5.0.0 to 5.5.1.
Running X-Pack? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 attacker might have been able to impersonate a legitimate user if the SAML Identity Provider allows for self registration with arbitrary identifiers and the attacker can register an account which an identifier that shares a suffix with a legitimate account. Both of those conditions must be true in order to exploit this flaw.
- Matched to
- X-Pack on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 9 published vulnerabilities listed under the name X-Pack, across 52 versions.
None of X-Pack's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track X-Pack. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.