Galaxy FDS Android SDK (XiaoMi/galaxy-fds-sdk-android) version 3.0.8 and prior disable TLS hostname verification when HTTPS is enabled (the default configuration). In GalaxyFDSClientImpl.createHttpClient(), the SDK configures Apache HttpClient with SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER, which accepts any valid TLS certificate regardless of hostname mismatch. Because HTTPS is enabled by default in FDSClientConfiguration, all applications using the SDK with default settings are affected. This vulnerability allows a man-in-the-middle attacker to intercept and modify SDK communications to Xiaomi FDS cloud storage endpoints, potentially exposing authentication credentials, file contents, and API responses. The XiaoMi/galaxy-fds-sdk-android open source project has reached end-of-life status.
Security readout for executives and security teams
Plain-English summary
Android apps using Xiaomi Galaxy FDS Android SDK 3.0.8 or earlier may trust the wrong TLS certificate hostname. A network attacker could intercept or alter cloud storage traffic, exposing credentials, file contents, or API responses. The project is reported as end-of-life, so remediation may require replacement rather than waiting for a routine update.
Executive priority
Treat as urgent for any production Android app using this SDK with sensitive storage traffic. The high CVSS score and end-of-life status increase business risk, but confirmed exposure depends on dependency use.
Technical view
The SDK’s GalaxyFDSClientImpl.createHttpClient() configures Apache HttpClient with SSLSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER while HTTPS is enabled by default in FDSClientConfiguration. This is CWE-297 and affects versions 3.0.8 and prior. The flaw enables MITM against SDK communications to Xiaomi FDS cloud storage endpoints.
Likely exposure
Exposure is limited to applications embedding Xiaomi Galaxy FDS Android SDK 3.0.8 or earlier. Default HTTPS settings are described as affected. The bundle does not prove all downstream Android apps or Xiaomi services are affected.
Exploitation context
The sources describe MITM potential, but KEV is false and no cited source confirms active exploitation. Exploitation requires attacker network position and a valid TLS certificate with a hostname mismatch, accepted because hostname verification is disabled.
Researcher notes
Evidence supports hostname verification bypass in the open source SDK and default HTTPS impact. The bundle does not name a fixed version, vendor patch, or observed exploitation. Avoid broad claims beyond Galaxy FDS Android SDK 3.0.8 and prior.
Mitigation direction
Inventory Android apps for galaxy-fds-sdk-android 3.0.8 or earlier.
Check Xiaomi or project guidance for any supported replacement or fix.
Plan migration away from the end-of-life SDK if no maintained release exists.
Avoid sending credentials or sensitive files through affected SDK builds.
Prioritize apps used on untrusted or mobile networks.
Validation and detection
Review dependency manifests for galaxy-fds-sdk-android and recorded versions.
Inspect SDK source or bundled code for ALLOW_ALL_HOSTNAME_VERIFIER use.
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.
cwe · low confidence lookup
CWE-297: 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.
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.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-297 · source CWE mapping
Improper Validation of Certificate with Host Mismatch
Improper Validation of Certificate with Host Mismatch represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.