{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-36174 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-36174 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-36174 is a high-severity vulnerability in n/a, published on 12 Sep 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-36174 and fix it if it is affected.\n\nWhat it is: CVE-2022-36174 is a high-severity vulnerability in n/a, published on 12 Sep 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-36174 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-36174/ (Markdown: https://insights.sbomify.com/CVE-2022-36174/index.md)","id":"CVE-2022-36174","markdown":"https://insights.sbomify.com/CVE-2022-36174/index.md","name":"CVE-2022-36174","record":{"aliases":["GHSA-xm2c-q8p4-pp7f"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FreshService Agent","requires_auth":"none","summary":"Attackers can bypass integrity checks in the FreshService Agent to execute arbitrary code via the update service.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"freshservice_agent","vendor":"freshworks"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"}],"description":"FreshService Windows Agent \u003c 2.11.0 and FreshService macOS Agent \u003c 4.2.0 and FreshService Linux Agent \u003c 3.3.0. are vulnerable to Broken integrity checking via the FreshAgent client and scheduled update service.","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":"Security feature bypass in n/a","id":"CVE-2022-36174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2022-36179"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2022-36173"},"products":["n/a"],"published":"2022-09-12","related":[{"cvss_score":8.1,"headline":"Weak cryptography in n/a","id":"CVE-2022-36173","kev_date_added":null,"published":"2022-09-12"}],"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 bypass integrity checks in the FreshService Agent to execute arbitrary code via the update service.","url":"https://insights.sbomify.com/CVE-2022-36174/"}