{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-22016 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-22016 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-22016 is a high-severity vulnerability in Rapid SCADA, published on 1 Feb 2024. 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-2024-22016 and fix it if it is affected.\n\nWhat it is: CVE-2024-22016 is a high-severity vulnerability in Rapid SCADA, published on 1 Feb 2024. 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-2024-22016 in the wild and no public exploit code.\n\nAffected product: Rapid SCADA. 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-2024-22016/ (Markdown: https://insights.sbomify.com/CVE-2024-22016/index.md)","id":"CVE-2024-22016","markdown":"https://insights.sbomify.com/CVE-2024-22016/index.md","name":"CVE-2024-22016","record":{"aliases":["GHSA-2rrv-22x6-4f23"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rapid SCADA","requires_auth":"low_privilege","summary":"An authorized user can write to the Scada directory, potentially leading to privilege escalation in Rapid SCADA.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"rapid_scada","vendor":"rapidscada"}],"cvss":{"score":7.8,"severity":"high","source":"cna","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-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"In Rapid Software LLC's Rapid SCADA versions prior to Version 5.8.4, an authorized user can write directly to the Scada directory. This may allow privilege escalation.","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":"Incorrect Permission Assignment for Critical Resource in Rapid SCADA","id":"CVE-2024-22016","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Node","id":"CVE-2024-22017"},"packages":[],"prev":{"headline":"Denial of service in Intel(R) DLB driver software","id":"CVE-2024-22015"},"products":["Rapid SCADA"],"published":"2024-02-01","related":[{"cvss_score":9.8,"headline":"Use of Hard-Coded Credentials in Rapid SCADA","id":"CVE-2024-21764","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":8.8,"headline":"Rapid SCADA Path Traversal","id":"CVE-2024-21852","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-22722","kev_date_added":null,"published":"2020-08-14"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-5313","kev_date_added":null,"published":"2018-03-08"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2024-47221","kev_date_added":null,"published":"2024-09-22"},{"cvss_score":6.5,"headline":"Relative Path Traversal in Rapid SCADA","id":"CVE-2024-22096","kev_date_added":null,"published":"2024-02-01"}],"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":"total"},"state":"PUBLISHED","updated":"2024-11-08","vendors":["Rapid Software LLC"]},"summary":"An authorized user can write to the Scada directory, potentially leading to privilege escalation in Rapid SCADA.","url":"https://insights.sbomify.com/CVE-2024-22016/"}