{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7512 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-7512 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-7512 is a critical vulnerability in Easergy T300 (Firmware version 1.5.2 and older), published on 16 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7512 and fix it if it is affected.\n\nWhat it is: CVE-2020-7512 is a critical vulnerability in Easergy T300 (Firmware version 1.5.2 and older), published on 16 Jun 2020. 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-2020-7512 in the wild and no public exploit code.\n\nAffected product: Easergy T300 (Firmware version 1.5.2 and older). 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-2020-7512/ (Markdown: https://insights.sbomify.com/CVE-2020-7512/index.md)","id":"CVE-2020-7512","markdown":"https://insights.sbomify.com/CVE-2020-7512/index.md","name":"CVE-2020-7512","record":{"aliases":["GHSA-f484-j6g8-m75p"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Easergy T300 firmware","requires_auth":"none","summary":"Attackers can exploit vulnerable third-party components in Easergy T300 firmware to potentially execute arbitrary code on the device.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"schneider","cpe":[{"product":"easergy_t300_firmware","vendor":"schneider-electric"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1103","name":"Use of Platform-Dependent Third Party Components"}],"description":"A CWE-1103: Use of Platform-Dependent Third Party Components with vulnerabilities vulnerability exists in Easergy T300 (Firmware version 1.5.2 and older) which could allow an attacker to exploit the component.","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":"Supply chain in Easergy T300 (Firmware version 1.5.2 and older)","id":"CVE-2020-7512","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Easergy T300 (Firmware version 1.5.2 and older)","id":"CVE-2020-7513"},"packages":[],"prev":{"headline":"Weak cryptography in Easergy T300 (Firmware version 1.5.2 and older)","id":"CVE-2020-7511"},"products":["Easergy T300 (Firmware version 1.5.2 and older)"],"published":"2020-06-16","related":[{"cvss_score":9.8,"headline":"Missing authorization in Easergy T300 (firmware 2.7 and older)","id":"CVE-2020-28215","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Missing authorization in Easergy T300 with firmware 2.7 and older","id":"CVE-2020-7561","kev_date_added":null,"published":"2020-11-19"},{"cvss_score":9.8,"headline":"Auth bypass in Easergy T300 (Firmware version 1.5.2 and older)","id":"CVE-2020-7508","kev_date_added":null,"published":"2020-06-16"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Easergy T300 (Firmware version 1.5.2 and older)","id":"CVE-2020-7503","kev_date_added":null,"published":"2020-06-16"},{"cvss_score":7.5,"headline":"Information disclosure in Easergy T300 (firmware 2.7 and older)","id":"CVE-2020-28216","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.5,"headline":"Information disclosure in Easergy T300 (firmware 2.7 and older)","id":"CVE-2020-28217","kev_date_added":null,"published":"2020-12-11"}],"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-04","vendors":["n/a"]},"summary":"Attackers can exploit vulnerable third-party components in Easergy T300 firmware to potentially execute arbitrary code on the device.","url":"https://insights.sbomify.com/CVE-2020-7512/"}