LiveActive security incident?Get immediate response
CVE Record

CVE-2017-5652: During a routine security analysis, it was found that one of the ports in Apache Impala (incubating) 2.7.0...

During a routine security analysis, it was found that one of the ports in Apache Impala (incubating) 2.7.0 to 2.8.0 sent data in plaintext even when the cluster was configured to use TLS. The port in question was used by the StatestoreSubscriber class which did not use the appropriate secure Thrift transport when TLS was turned on. It was therefore possible for an adversary, with access to the network, to eavesdrop on the packets going to and coming from that port and view the data in plaintext.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Apache Impala 2.7.0 through 2.8.0 could leak some cluster traffic in readable form even when TLS was enabled. A network-positioned attacker could eavesdrop on traffic to and from the affected StatestoreSubscriber port. The sources do not report active exploitation or provide CVSS scoring. Exposure is most likely in organizations running Apache Impala incubating 2.7.0 or 2.8.0 with TLS enabled, where cluster network traffic is reachable by untrusted users, compromised hosts, or shared infrastructure. Prioritize remediation for affected Impala clusters on shared or less-trusted networks. Business risk is confidentiality loss from data visible on internal traffic, not remote code execution. Urgency is lower where cluster networks are tightly isolated, but TLS assumptions should be corrected. Mitigation focus: Inventory Apache Impala deployments and identify versions 2.7.0 and 2.8.0.; Check Apache or distribution vendor guidance for the appropriate fixed release or mitigation.; Restrict network access to Impala cluster communication ports to trusted hosts only..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2017-5652 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache Impala2.7.0 to 2.8.0 incubatingListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.