{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-5146 exists.","fix":"No fix has been published for CVE-2017-5146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5146 is a high-severity vulnerability in Carlo Gavazzi VMU-C EM and VMU-C PV, published on 13 Feb 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-5146 and fix it if it is affected.\n\nWhat it is: CVE-2017-5146 is a high-severity vulnerability in Carlo Gavazzi VMU-C EM and VMU-C PV, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-5146 exists.\n\nAffected product: Carlo Gavazzi VMU-C EM and VMU-C PV. 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-5146/ (Markdown: https://insights.sbomify.com/CVE-2017-5146/index.md)","id":"CVE-2017-5146","markdown":"https://insights.sbomify.com/CVE-2017-5146/index.md","name":"CVE-2017-5146","record":{"aliases":["GHSA-c93j-r7rc-86j9"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Carlo Gavazzi VMU-C","requires_auth":"none","summary":"Attackers can read sensitive information stored in clear text on Carlo Gavazzi VMU-C energy and PV monitoring devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"vmu-c_em_firmware","vendor":"carlosgavazzi"},{"product":"vmu-c_pv_firmware","vendor":"carlosgavazzi"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/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":"An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware Version A17. Sensitive information is stored in clear-text.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":null,"kind":"metasploit","ref":"auxiliary/scanner/http/gavazzi_em_login_loot","stars":null,"title":"Carlo Gavazzi Energy Meters - Login Brute Force, Extract Info and Dump Plant Database"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in Carlo Gavazzi VMU-C EM and VMU-C PV","id":"CVE-2017-5146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in AzeoTech DAQFactory","id":"CVE-2017-5147"},"packages":[],"prev":{"headline":"Cross-site request forgery in Carlo Gavazzi VMU-C EM and VMU-C PV","id":"CVE-2017-5145"},"products":["Carlo Gavazzi VMU-C EM and VMU-C PV"],"published":"2017-02-13","related":[{"cvss_score":10,"headline":"Cross-site request forgery in Carlo Gavazzi VMU-C EM and VMU-C PV","id":"CVE-2017-5145","kev_date_added":null,"published":"2017-02-13"},{"cvss_score":9.8,"headline":"Missing authorization in Carlo Gavazzi VMU-C EM and VMU-C PV","id":"CVE-2017-5144","kev_date_added":null,"published":"2017-02-13"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can read sensitive information stored in clear text on Carlo Gavazzi VMU-C energy and PV monitoring devices.","url":"https://insights.sbomify.com/CVE-2017-5146/"}