{"answers":{"affected":"It affects 17 products.","exploited":"There is no known exploitation of CVE-2022-29958 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29958 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29958 is a critical code injection vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29958 and fix it if it is affected.\n\nWhat it is: CVE-2022-29958 is a critical code injection vulnerability in n/a, published on 26 Jul 2022. 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-2022-29958 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-2022-29958/ (Markdown: https://insights.sbomify.com/CVE-2022-29958/index.md)","id":"CVE-2022-29958","markdown":"https://insights.sbomify.com/CVE-2022-29958/index.md","name":"CVE-2022-29958","record":{"aliases":["GHSA-vq3c-fhqv-p29r"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JTEKT TOYOPUC PLC","requires_auth":"none","summary":"Attackers can inject arbitrary machine code into JTEKT TOYOPUC PLCs via unauthenticated CMPLink/TCP protocol, gaining full control over the CPU module.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nano_10gx_tuc-1157_firmware","vendor":"jtekt"},{"product":"nano_cpu_tuc-6941_firmware","vendor":"jtekt"},{"product":"pc10b-p_tcc-6373_firmware","vendor":"jtekt"},{"product":"pc10b_tcc-1021_firmware","vendor":"jtekt"},{"product":"pc10e_tcc-4737_firmware","vendor":"jtekt"},{"product":"pc10el_tcc-4747_firmware","vendor":"jtekt"},{"product":"pc10g-cpu_tcc-6353_firmware","vendor":"jtekt"},{"product":"pc10ge_tcc-6464_firmware","vendor":"jtekt"},{"product":"pc10p-dp-io_tcc-6752_firmware","vendor":"jtekt"},{"product":"pc10p-dp_tcc-6726_firmware","vendor":"jtekt"},{"product":"pc10p_tcc-6372_firmware","vendor":"jtekt"},{"product":"pc10pe-1616p_tcc-1102_firmware","vendor":"jtekt"},{"product":"pc10pe_tcc-1101_firmware","vendor":"jtekt"},{"product":"pc3jx-d_tcc-6902_firmware","vendor":"jtekt"},{"product":"pc3jx_tcc-6901_firmware","vendor":"jtekt"},{"product":"pcdl_tkc-6688_firmware","vendor":"jtekt"},{"product":"plus_cpu_tcc-6740_firmware","vendor":"jtekt"}],"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-345","name":"Insufficient Verification of Data Authenticity"}],"description":"JTEKT TOYOPUC PLCs through 2022-04-29 do not ensure data integrity. They utilize the unauthenticated CMPLink/TCP protocol for engineering purposes, including downloading projects and control logic to the PLC. Control logic is downloaded to the PLC on a block-by-block basis with a given memory address and a blob of machine code. The logic that is downloaded to the PLC is not cryptographically authenticated, allowing an attacker to execute arbitrary machine code on the PLC's CPU module in the context of the runtime. In the case of the PC10G-CPU, and likely for other CPU modules of the TOYOPUC family, a processor without MPU or MMU is used and this no memory protection or privilege-separation capabilities are available, giving an attacker full control over the CPU.","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":"Code injection in n/a","id":"CVE-2022-29958","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-29959"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-29957"},"products":["n/a"],"published":"2022-07-26","related":[{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2022-29951","kev_date_added":null,"published":"2022-07-26"}],"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-03","vendors":["n/a"]},"summary":"Attackers can inject arbitrary machine code into JTEKT TOYOPUC PLCs via unauthenticated CMPLink/TCP protocol, gaining full control over the CPU module.","url":"https://insights.sbomify.com/CVE-2022-29958/"}