{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29957 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29957 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29957 is a high-severity missing authorization vulnerability in n/a, published on 26 Jul 2022. 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-29957 and fix it if it is affected.\n\nWhat it is: CVE-2022-29957 is a high-severity missing authorization vulnerability in n/a, published on 26 Jul 2022. 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-29957 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-29957/ (Markdown: https://insights.sbomify.com/CVE-2022-29957/index.md)","id":"CVE-2022-29957","markdown":"https://insights.sbomify.com/CVE-2022-29957/index.md","name":"CVE-2022-29957","record":{"aliases":["GHSA-jqmm-x5xp-f3pq"],"analysis":{"component_type":"ics_ot","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Emerson DeltaV DCS","requires_auth":"low_privilege","summary":"Attackers can invoke critical system functions like firmware upgrades and restarts without authentication due to missing security controls in proprietary protocols.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"deltav_distributed_control_system","vendor":"emerson"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The Emerson DeltaV Distributed Control System (DCS) through 2022-04-29 mishandles authentication. It utilizes several proprietary protocols for a wide variety of functionality. These protocols include Firmware upgrade (18508/TCP, 18518/TCP); Plug-and-Play (18510/UDP); Hawk services (18507/UDP); Management (18519/TCP); Cold restart (18512/UDP); SIS communications (12345/TCP); and Wireless Gateway Protocol (18515/UDP). None of these protocols have any authentication features, allowing any attacker capable of communicating with the ports in question to invoke (a subset of) desired functionality.","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":"Missing authorization in n/a","id":"CVE-2022-29957","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2022-29958"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-29953"},"products":["n/a"],"published":"2022-07-26","related":[{"cvss_score":6.1,"headline":"Emerson DeltaV Missing Authentication for Critical Function","id":"CVE-2021-26264","kev_date_added":null,"published":"2022-01-28"},{"cvss_score":5.5,"headline":"Weak cryptography in n/a","id":"CVE-2022-29965","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 invoke critical system functions like firmware upgrades and restarts without authentication due to missing security controls in proprietary protocols.","url":"https://insights.sbomify.com/CVE-2022-29957/"}