{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2022-29952 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29952 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29952 is a critical missing authorization vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29952 and fix it if it is affected.\n\nWhat it is: CVE-2022-29952 is a critical missing authorization vulnerability in n/a, published on 26 Jul 2022. 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-2022-29952 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-29952/ (Markdown: https://insights.sbomify.com/CVE-2022-29952/index.md)","id":"CVE-2022-29952","markdown":"https://insights.sbomify.com/CVE-2022-29952/index.md","name":"CVE-2022-29952","record":{"aliases":["GHSA-xgjg-q85m-vvmx"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Bently Nevada monitoring","requires_auth":"none","summary":"Attackers can access configuration and historical data via unauthenticated TDI protocols on Bently Nevada condition monitoring equipment.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bently_nevada_3701\\/40_firmware","vendor":"bakerhughes"},{"product":"bently_nevada_3701\\/44_firmware","vendor":"bakerhughes"},{"product":"bently_nevada_3701\\/46_firmware","vendor":"bakerhughes"},{"product":"bently_nevada_60m100_firmware","vendor":"bakerhughes"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Bently Nevada condition monitoring equipment through 2022-04-29 mishandles authentication. It utilizes the TDI command and data protocols (60005/TCP, 60007/TCP) for communications between the monitoring controller and System 1 and/or Bently Nevada Monitor Configuration (BNMC) software. These protocols provide configuration management and historical data related functionality. Neither protocol has 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-29952","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":"Hardcoded credentials in n/a","id":"CVE-2022-29953"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-29951"},"products":["n/a"],"published":"2022-07-26","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-29953","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 access configuration and historical data via unauthenticated TDI protocols on Bently Nevada condition monitoring equipment.","url":"https://insights.sbomify.com/CVE-2022-29952/"}