{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2022-4332 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-4332 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4332 is a medium-severity vulnerability in Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x, published on 1 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-4332 and fix it if it is affected.\n\nWhat it is: CVE-2022-4332 is a medium-severity vulnerability in Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x, published on 1 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-4332 in the wild and no public exploit code.\n\nAffected product: Sprecher Automation SPRECON-E-C/P/T3 CPU PU244x. 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-4332/ (Markdown: https://insights.sbomify.com/CVE-2022-4332/index.md)","id":"CVE-2022-4332","markdown":"https://insights.sbomify.com/CVE-2022-4332/index.md","name":"CVE-2022-4332","record":{"aliases":["GHSA-73v7-m7qm-qq9g"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Industrial control CPU","requires_auth":"none","summary":"Attackers with physical access can bypass firmware verification to execute arbitrary code and gain full control of the device.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"sprecon-e-c_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-p_dl6-1_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-p_dq6-1_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-p_ds6-0_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-t3_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-tc_ax-3110_firmware","vendor":"sprecher-automation"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"In Sprecher Automation SPRECON-E-C/P/T3 CPU in variant PU244x a vulnerable firmware verification has been identified. Through physical access and hardware manipulation, an attacker might be able to bypass hardware-based code verification and thus inject and execute arbitrary code and gain full access of the device.","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":"Sprecher: Vulnerable firmware verification","id":"CVE-2022-4332","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Sprecher: Sprecon maintenance access with hardcoded credentials","id":"CVE-2022-4333"},"packages":[],"prev":{"headline":"Auth bypass in GitLab","id":"CVE-2022-4331"},"products":["SPRECON-E-C/P/T3 CPU PU244x"],"published":"2023-06-01","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in SPRECON-E-C","id":"CVE-2025-41742","kev_date_added":null,"published":"2025-12-02"},{"cvss_score":9.8,"headline":"Sprecher: Sprecon maintenance access with hardcoded credentials","id":"CVE-2022-4333","kev_date_added":null,"published":"2023-06-01"},{"cvss_score":9.1,"headline":"Sprecher Automation: SPRECON-E series has static default key material for TLS connections","id":"CVE-2025-41744","kev_date_added":null,"published":"2025-12-02"},{"cvss_score":6.5,"headline":"Improper Privilege Management vulnerability in Sprecher Automation SPRECON-E","id":"CVE-2024-6758","kev_date_added":null,"published":"2024-08-12"},{"cvss_score":4,"headline":"Sprecher Automation: SPRECON-E series prone to weak encryption of update files","id":"CVE-2025-41743","kev_date_added":null,"published":"2025-12-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-10","vendors":["Sprecher Automation"]},"summary":"Attackers with physical access can bypass firmware verification to execute arbitrary code and gain full control of the device.","url":"https://insights.sbomify.com/CVE-2022-4332/"}