{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11578 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11578 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11578 is a medium-severity vulnerability in n/a, published on 2 Jul 2019. 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-11578 and fix it if it is affected.\n\nWhat it is: CVE-2017-11578 is a medium-severity vulnerability in n/a, published on 2 Jul 2019. 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-11578 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-2017-11578/ (Markdown: https://insights.sbomify.com/CVE-2017-11578/index.md)","id":"CVE-2017-11578","markdown":"https://insights.sbomify.com/CVE-2017-11578/index.md","name":"CVE-2017-11578","record":{"aliases":["GHSA-hjx2-43ph-gqjc"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IoT blood pressure monitor","requires_auth":"none","summary":"An attacker on the local network can sniff Wi-Fi credentials transmitted in plaintext via the device's unencrypted web management interface.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wi-fi_blood_pressure_monitor_firmware","vendor":"blipcare"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"It was discovered as a part of the research on IoT devices in the most recent firmware for Blipcare device that the device allows to connect to web management interface on a non-SSL connection using plain text HTTP protocol. The user uses the web management interface of the device to provide the user's Wi-Fi credentials so that the device can connect to it and have Internet access. This device acts as a Wireless Blood pressure monitor and is used to measure blood pressure levels of a person. This allows an attacker who is connected to the Blipcare's device wireless network to easily sniff these values using a 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":"Information disclosure in n/a","id":"CVE-2017-11578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"In the most recent firmware for Blipcare, the device provides an open Wireless network called \"Blip\" for communicating with the device.","id":"CVE-2017-11579"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-11577"},"products":["n/a"],"published":"2019-07-02","related":[{"cvss_score":7.1,"headline":"In the most recent firmware for Blipcare, the device provides an open Wireless network called \"Blip\" for communicating with the device.","id":"CVE-2017-11579","kev_date_added":null,"published":"2019-07-02"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2017-11580","kev_date_added":null,"published":"2019-07-02"}],"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":"An attacker on the local network can sniff Wi-Fi credentials transmitted in plaintext via the device's unencrypted web management interface.","url":"https://insights.sbomify.com/CVE-2017-11578/"}