{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34757 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34757 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34757 is a medium-severity vulnerability in Schneider Electric Easergy P5, published on 13 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-34757 and fix it if it is affected.\n\nWhat it is: CVE-2022-34757 is a medium-severity vulnerability in Schneider Electric Easergy P5, published on 13 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-34757 in the wild and no public exploit code.\n\nAffected product: Schneider Electric Easergy P5. 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-34757/ (Markdown: https://insights.sbomify.com/CVE-2022-34757/index.md)","id":"CVE-2022-34757","markdown":"https://insights.sbomify.com/CVE-2022-34757/index.md","name":"CVE-2022-34757","record":{"aliases":["GHSA-8g4c-686x-3qcc"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Schneider Easergy P5","requires_auth":"none","summary":"Weak SSH cipher suites in Schneider Easergy P5 allow attackers to observe protected communication details.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"schneider","cpe":[{"product":"easergy_p5_firmware","vendor":"schneider-electric"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"A CWE-327: Use of a Broken or Risky Cryptographic Algorithm vulnerability exists where weak cipher suites can be used for the SSH connection between Easergy Pro software and the device, which may allow an attacker to observe protected communication details. Affected Products: Easergy P5 (V01.401.102 and prior)","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":"Weak cryptography in Easergy P5","id":"CVE-2022-34757","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Easergy P5","id":"CVE-2022-34758"},"packages":[],"prev":{"headline":"Memory corruption in Easergy P5","id":"CVE-2022-34756"},"products":["Easergy P5"],"published":"2022-07-13","related":[{"cvss_score":8.8,"headline":"Memory corruption in Easergy P5","id":"CVE-2022-34756","kev_date_added":null,"published":"2022-07-13"},{"cvss_score":8.8,"headline":"Memory corruption in Easergy P5 (All firmware versions prior to V01.401.101)","id":"CVE-2022-22723","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":7.5,"headline":"Hardcoded credentials in Easergy P5","id":"CVE-2022-22722","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":5.1,"headline":"Denial of service in Easergy P5","id":"CVE-2022-34758","kev_date_added":null,"published":"2022-07-13"}],"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-09-16","vendors":["Schneider Electric"]},"summary":"Weak SSH cipher suites in Schneider Easergy P5 allow attackers to observe protected communication details.","url":"https://insights.sbomify.com/CVE-2022-34757/"}