X Pack Security
Approved changes feed: RSS · Atom
cpe:2.3:a:elastic:x-pack_security:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Elastic (1d0b8d2a-fd47-5b20-b005-34326f9bd037) |
|---|---|
| Product | X Pack Security (2798a057-f4b2-5280-91d6-644e61d62df1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-3822 |
vulnerable | 2026-06-03 14:38:50.473285 |
Details available
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.
Published: 2018-03-30T20:00:00.000Z
Updated: 2024-08-05T04:57:23.752Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-8441 |
vulnerable | 2026-06-03 14:37:39.996667 |
Details available
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.
Published: 2017-06-05T14:00:00.000Z
Updated: 2024-08-05T16:34:22.945Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-8438 |
vulnerable | 2026-06-03 14:37:39.985847 |
Details available
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 specified user specified in a run_as request. If a role has been created using a template that contains the _user properties, the behavior of run_as will be incorrect. Additionally if the run_as user specified does not exist, the transition will not happen.
Published: 2017-06-05T14:00:00.000Z
Updated: 2024-08-05T16:34:22.961Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.