{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2025-41743 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-41743 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-41743 is a medium-severity vulnerability in Sprecher Automation SPRECON-E-C, published on 2 Dec 2025. 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-2025-41743 and fix it if it is affected.\n\nWhat it is: CVE-2025-41743 is a medium-severity vulnerability in Sprecher Automation SPRECON-E-C, published on 2 Dec 2025. 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-2025-41743 in the wild and no public exploit code.\n\nAffected product: Sprecher Automation SPRECON-E-C. 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-2025-41743/ (Markdown: https://insights.sbomify.com/CVE-2025-41743/index.md)","id":"CVE-2025-41743","markdown":"https://insights.sbomify.com/CVE-2025-41743/index.md","name":"CVE-2025-41743","record":{"aliases":["GHSA-v2x4-9r4m-m784"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SPRECON-E protection relay","requires_auth":"none","summary":"A local unprivileged attacker can extract limited architectural information from update images due to insufficient encryption strength in SPRECON-E devices.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERTVDE","cpe":[{"product":"sprecon-e-c_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-p_firmware","vendor":"sprecher-automation"},{"product":"sprecon-e-t3_firmware","vendor":"sprecher-automation"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"Insufficient encryption strength in Sprecher Automation SPRECON-E-C, SPRECON-E-P, and SPRECON-E-T3 allows a local unprivileged attacker to extract data from update images and thus obtain limited information about the architecture and internal processes.","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 Automation: SPRECON-E series prone to weak encryption of update files","id":"CVE-2025-41743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Sprecher Automation: SPRECON-E series has static default key material for TLS connections","id":"CVE-2025-41744"},"packages":[],"prev":{"headline":"Hardcoded credentials in SPRECON-E-C","id":"CVE-2025-41742"},"products":["SPRECON-E-C","SPRECON-E-P","SPRECON-E-T3"],"published":"2025-12-02","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.8,"headline":"Sprecher: Vulnerable firmware verification","id":"CVE-2022-4332","kev_date_added":null,"published":"2023-06-01"},{"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"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-12-02","vendors":["Sprecher Automation"]},"summary":"A local unprivileged attacker can extract limited architectural information from update images due to insufficient encryption strength in SPRECON-E devices.","url":"https://insights.sbomify.com/CVE-2025-41743/"}