LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3182: On the iOS platform, the ThreatMetrix SDK versions prior to 3.2 fail to validate SSL certificates provided by HTTPS connections, which may allow an attacker to perform a man-in-the-middle (MITM) attack

On the iOS platform, the ThreatMetrix SDK versions prior to 3.2 fail to validate SSL certificates provided by HTTPS connections, which may allow an attacker to perform a man-in-the-middle (MITM) attack. ThreatMetrix is a security library for mobile applications, which aims to provide fraud prevention and device identity capabilities. The ThreatMetrix SDK versions prior to 3.2 do not validate SSL certificates on the iOS platform. An affected application will communicate with https://h-sdk.online-metrix.net, regardless of whether the connection is secure or not. An attacker on the same network as or upstream from the iOS device may be able to view or modify ThreatMetrix network traffic that should have been protected by HTTPS.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some iOS apps using older ThreatMetrix SDK versions may not properly check HTTPS certificates. That can let someone positioned on the same network or upstream intercept or alter ThreatMetrix traffic that should be encrypted. The issue affects fraud-prevention telemetry, so the business concern is loss of trust in device identity and fraud signals.

Executive priority

Prioritize if your iOS apps rely on ThreatMetrix for fraud prevention or device identity. The issue can undermine telemetry integrity, but urgency is lower without evidence of broad active exploitation in the supplied sources.

Technical view

CVE-2017-3182 is a CWE-295 certificate validation failure in ThreatMetrix SDK for iOS versions prior to 3.2. Affected apps communicate with https://h-sdk.online-metrix.net without validating SSL certificates, allowing a same-network or upstream attacker to view or modify ThreatMetrix HTTPS traffic.

Likely exposure

Exposure is limited to iOS applications that embedded ThreatMetrix SDK versions prior to 3.2. Organizations should check mobile app dependency records, vendor attestations, and released app versions. The provided sources do not identify specific downstream apps.

Exploitation context

The sources describe a man-in-the-middle risk for attackers on the same network as the iOS device or upstream from it. The CVE bundle marks KEV as false, and no supplied source states active exploitation.

Researcher notes

The record has no CVSS score in the supplied bundle. Treat affected-version interpretation carefully: the narrative states versions prior to 3.2 are vulnerable. Focus validation on embedded iOS SDK versions and certificate validation behavior for ThreatMetrix traffic.

Mitigation direction

  • Identify iOS apps using ThreatMetrix SDK versions prior to 3.2.
  • Upgrade affected iOS apps to ThreatMetrix SDK 3.2 or later.
  • Rebuild and redistribute affected mobile app releases after SDK update.
  • Check CERT and vendor guidance for any additional remediation details.

Validation and detection

  • Review SBOMs, dependency manifests, and vendor records for ThreatMetrix SDK version evidence.
  • Confirm released iOS app builds no longer include SDK versions prior to 3.2.
  • Validate that ThreatMetrix connections enforce proper certificate validation in approved testing.
  • Document whether https://h-sdk.online-metrix.net traffic exists in affected app workflows.
Prepared
Confidence
high
Sources
4

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-295: 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 lookup
cve · low confidence lookup

CVE-2017-3182 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
3Source 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
ThreatMetrixSDK3.2Listed
Weakness

CWE details

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

CWE-295 · source CWE mapping

Improper Certificate Validation

Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.