{"answers":{"affected":"It affects 17 products.","exploited":"There is no known exploitation of CVE-2013-4651 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-4651 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-4651 is a medium-severity vulnerability in n/a, published on 31 Jul 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-4651 and fix it if it is affected.\n\nWhat it is: CVE-2013-4651 is a medium-severity vulnerability in n/a, published on 31 Jul 2013. 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-2013-4651 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-2013-4651/ (Markdown: https://insights.sbomify.com/CVE-2013-4651/index.md)","id":"CVE-2013-4651","markdown":"https://insights.sbomify.com/CVE-2013-4651/index.md","name":"CVE-2013-4651","record":{"aliases":["GHSA-fg5w-4qj3-jgj3"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Siemens Scalance W7xx","requires_auth":"none","summary":"Remote attackers can intercept SSL traffic via man-in-the-middle attacks due to a shared hardcoded X.509 certificate in Siemens Scalance W7xx devices.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"scalance_w700_series_firmware","vendor":"siemens"},{"product":"scalance_w744-1","vendor":"siemens"},{"product":"scalance_w744-1pro","vendor":"siemens"},{"product":"scalance_w746-1","vendor":"siemens"},{"product":"scalance_w746-1pro","vendor":"siemens"},{"product":"scalance_w747-1","vendor":"siemens"},{"product":"scalance_w747-1rr","vendor":"siemens"},{"product":"scalance_w784-1","vendor":"siemens"},{"product":"scalance_w784-1rr","vendor":"siemens"},{"product":"scalance_w786-1pro","vendor":"siemens"},{"product":"scalance_w786-2pro","vendor":"siemens"},{"product":"scalance_w786-2rr","vendor":"siemens"},{"product":"scalance_w786-3pro","vendor":"siemens"},{"product":"scalance_w788-1pro","vendor":"siemens"},{"product":"scalance_w788-1rr","vendor":"siemens"},{"product":"scalance_w788-2pro","vendor":"siemens"},{"product":"scalance_w788-2rr","vendor":"siemens"}],"cvss":{"score":6.6,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:C","version":"2.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"Siemens Scalance W7xx devices with firmware before 4.5.4 use the same hardcoded X.509 certificate across different customers' installations, which makes it easier for remote attackers to conduct man-in-the-middle attacks against SSL sessions by leveraging the certificate's trust relationship.","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-2013-4651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2013"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2013-4652"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2013-4650"},"products":["n/a"],"published":"2013-07-31","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2013-4652","kev_date_added":null,"published":"2013-07-31"}],"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-17","vendors":["n/a"]},"summary":"Remote attackers can intercept SSL traffic via man-in-the-middle attacks due to a shared hardcoded X.509 certificate in Siemens Scalance W7xx devices.","url":"https://insights.sbomify.com/CVE-2013-4651/"}