{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6870 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-6870 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-6870 is a high-severity vulnerability in SIMATIC WinCC Sm@rtClient for Android, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-6870 and fix it if it is affected.\n\nWhat it is: CVE-2017-6870 is a high-severity vulnerability in SIMATIC WinCC Sm@rtClient for Android, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-6870 in the wild and no public exploit code.\n\nAffected product: SIMATIC WinCC Sm@rtClient for Android. 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-6870/ (Markdown: https://insights.sbomify.com/CVE-2017-6870/index.md)","id":"CVE-2017-6870","markdown":"https://insights.sbomify.com/CVE-2017-6870/index.md","name":"CVE-2017-6870","record":{"aliases":["GHSA-fhhq-wp7p-mxf8"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens WinCC Android Client","requires_auth":"none","summary":"Attackers can read and modify data in TLS sessions via Man-in-the-Middle attacks due to weak cryptography in the Siemens WinCC Android client.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"siemens","cpe":[{"product":"simatic_wincc_sm\\@rtclient","vendor":"siemens"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-300","name":"Channel Accessible by Non-Endpoint"}],"description":"A vulnerability was discovered in Siemens SIMATIC WinCC Sm@rtClient for Android (All versions before V1.0.2.2). The existing TLS protocol implementation could allow an attacker to read and modify data within a TLS session while performing a Man-in-the-Middle (MitM) attack.","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 SIMATIC WinCC Sm@rtClient for Android","id":"CVE-2017-6870","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":"Auth bypass in SIMATIC WinCC Sm@rtClient for Android, SIMATIC WinCC Sm@rtClient Lite for Android","id":"CVE-2017-6871"},"packages":[],"prev":{"headline":"File upload in ViewPort for Web Office Portal before revision number 1453","id":"CVE-2017-6869"},"products":["SIMATIC WinCC Sm@rtClient for Android"],"published":"2017-08-08","related":[{"cvss_score":5.4,"headline":"Auth bypass in SIMATIC WinCC Sm@rtClient for Android, SIMATIC WinCC Sm@rtClient Lite for Android","id":"CVE-2017-6871","kev_date_added":null,"published":"2017-08-08"},{"cvss_score":2.1,"headline":"Information disclosure in n/a","id":"CVE-2015-5084","kev_date_added":null,"published":"2015-08-03"},{"cvss_score":2.1,"headline":"Information disclosure in n/a","id":"CVE-2014-5231","kev_date_added":null,"published":"2015-01-14"},{"cvss_score":1.9,"headline":"Auth bypass in n/a","id":"CVE-2014-5232","kev_date_added":null,"published":"2015-01-14"},{"cvss_score":1.9,"headline":"Information disclosure in n/a","id":"CVE-2014-5233","kev_date_added":null,"published":"2015-01-14"}],"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":["n/a"]},"summary":"Attackers can read and modify data in TLS sessions via Man-in-the-Middle attacks due to weak cryptography in the Siemens WinCC Android client.","url":"https://insights.sbomify.com/CVE-2017-6870/"}