{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2015-5084 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-5084 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-5084 is a low-severity vulnerability in n/a, published on 3 Aug 2015. 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-2015-5084 and fix it if it is affected.\n\nWhat it is: CVE-2015-5084 is a low-severity vulnerability in n/a, published on 3 Aug 2015. 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-2015-5084 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2015-5084/ (Markdown: https://insights.sbomify.com/CVE-2015-5084/index.md)","id":"CVE-2015-5084","markdown":"https://insights.sbomify.com/CVE-2015-5084/index.md","name":"CVE-2015-5084","record":{"aliases":["GHSA-mq34-fv42-jm6r"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Siemens WinCC Sm@rtClient","requires_auth":"none","summary":"Physically proximate attackers can obtain sensitive information from Siemens SIMATIC WinCC Sm@rtClient Android apps due to improper password storage.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"simatic_wincc_sm\\@rtclient","vendor":"siemens"},{"product":"simatic_wincc_sm\\@rtclient_lite","vendor":"siemens"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Siemens SIMATIC WinCC Sm@rtClient and Sm@rtClient Lite applications before 01.00.01.00 for Android do not properly store passwords, which allows physically proximate attackers to obtain sensitive information via unspecified vectors.","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":"Information disclosure in n/a","id":"CVE-2015-5084","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":4,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2015-5085"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2015-5082"},"products":["n/a"],"published":"2015-08-03","related":[{"cvss_score":7.4,"headline":"Weak cryptography in SIMATIC WinCC Sm@rtClient for Android","id":"CVE-2017-6870","kev_date_added":null,"published":"2017-08-08"},{"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-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-06","vendors":["n/a"]},"summary":"Physically proximate attackers can obtain sensitive information from Siemens SIMATIC WinCC Sm@rtClient Android apps due to improper password storage.","url":"https://insights.sbomify.com/CVE-2015-5084/"}