Security readout for executives and security teams
Plain-English summary
A crafted Kibana URL could lead a user to a faulty Kibana login screen. If they enter credentials, those credentials may appear in the browser URL and be captured in access logs or seen by untrusted parties.
Executive priority
Prioritize remediation where Kibana is used for security or operational data, because credential leakage can lead to broader unauthorized access even without direct remote code execution.
Technical view
Kibana X-Pack Security before 5.4.3 could expose submitted credentials in the URL after a crafted Kibana URL redirects to an improperly initialized login screen. The listed weakness is CWE-598, use of GET request method with sensitive query strings.
Likely exposure
Exposure is limited to Elastic Kibana deployments using X-Pack Security versions before 5.4.3, especially where users can be induced to open crafted Kibana links.
Exploitation context
The source bundle does not show CISA KEV listing, CVSS scoring, public exploit status, or confirmed active exploitation. The described risk requires user interaction and credential entry on the affected login screen.
Researcher notes
Evidence is sparse: no CVSS vector is provided, and the only affected range listed is before 5.4.3. Focus validation on version exposure, user interaction risk, and log handling for sensitive URL data.
Mitigation direction
- Upgrade Kibana X-Pack Security to version 5.4.3 or later.
- Review Elastic security guidance for any environment-specific instructions.
- Treat exposed credentials as compromised and rotate them promptly.
- Restrict access to Kibana and its access logs to trusted administrators.
Validation and detection
- Inventory Kibana deployments and confirm X-Pack Security versions.
- Identify any instances running versions earlier than 5.4.3.
- Review Kibana access logs for credential-like values in URLs.
- Confirm access logs are protected from untrusted readers.
- Check whether affected users need credential rotation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-598: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-8443 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.elastic.co/community/securityCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of HTTP Request With Sensitive Query String
Use of HTTP Request With Sensitive Query String represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.