{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-7574 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7574 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7574 is a critical vulnerability in n/a, published on 6 Apr 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-7574 and fix it if it is affected.\n\nWhat it is: CVE-2017-7574 is a critical vulnerability in n/a, published on 6 Apr 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-7574 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-7574/ (Markdown: https://insights.sbomify.com/CVE-2017-7574/index.md)","id":"CVE-2017-7574","markdown":"https://insights.sbomify.com/CVE-2017-7574/index.md","name":"CVE-2017-7574","record":{"aliases":["GHSA-v5jg-gm3q-h894"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PLC programming software","requires_auth":"none","summary":"Attackers can decrypt protected project files using a hardcoded AES key to retrieve passwords, allowing unauthorized access and modification of PLC projects.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"modicon_tm221ce16r_firmware","vendor":"schneider-electric"},{"product":"somachine","vendor":"schneider-electric"}],"cvss":{"score":10,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"Schneider Electric SoMachine Basic 1.4 SP1 and Schneider Electric Modicon TM221CE16R 1.3.3.3 devices have a hardcoded-key vulnerability. The Project Protection feature is used to prevent unauthorized users from opening an XML protected project file, by prompting the user for a password. This XML file is AES-CBC encrypted; however, the key used for encryption (SoMachineBasicSoMachineBasicSoMa) cannot be changed. After decrypting the XML file with this key, the user password can be found in the decrypted data. After reading the user password, the project can be opened and modified with the Schneider product.","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":"Hardcoded credentials in n/a","id":"CVE-2017-7574","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-7575"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2017-7572"},"products":["n/a"],"published":"2017-04-06","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2017-7575","kev_date_added":null,"published":"2017-04-06"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-29","vendors":["n/a"]},"summary":"Attackers can decrypt protected project files using a hardcoded AES key to retrieve passwords, allowing unauthorized access and modification of PLC projects.","url":"https://insights.sbomify.com/CVE-2017-7574/"}