{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3182 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3182 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3182 is a medium-severity vulnerability in ThreatMetrix SDK, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-3182 and fix it if it is affected.\n\nWhat it is: CVE-2017-3182 is a medium-severity vulnerability in ThreatMetrix SDK, published on 24 Jul 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-3182 in the wild and no public exploit code.\n\nAffected product: ThreatMetrix SDK. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-3182/ (Markdown: https://insights.sbomify.com/CVE-2017-3182/index.md)","id":"CVE-2017-3182","markdown":"https://insights.sbomify.com/CVE-2017-3182/index.md","name":"CVE-2017-3182","record":{"aliases":["GHSA-75m3-p5wf-c6mc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"iOS fraud prevention SDK","requires_auth":"none","summary":"An attacker can perform man-in-the-middle attacks to view or modify data because the iOS SDK fails to validate SSL certificates.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"threatmetrix_sdk","vendor":"threatmetrix"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Weak cryptography in SDK","id":"CVE-2017-3182","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in XRT Treasury","id":"CVE-2017-3183"},"packages":[],"prev":{"headline":"SQL injection in Spotfire Analyst","id":"CVE-2017-3181"},"products":["SDK"],"published":"2018-07-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["ThreatMetrix"]},"summary":"An attacker can perform man-in-the-middle attacks to view or modify data because the iOS SDK fails to validate SSL certificates.","url":"https://insights.sbomify.com/CVE-2017-3182/"}