{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2175 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2175 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2175 is a high-severity vulnerability in INFORMATION-TECHNOLOGY PROMOTION AGENCY, JAPAN (IPA) Empirical Project Monitor - eXtended, published on 22 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-2175 and fix it if it is affected.\n\nWhat it is: CVE-2017-2175 is a high-severity vulnerability in INFORMATION-TECHNOLOGY PROMOTION AGENCY, JAPAN (IPA) Empirical Project Monitor - eXtended, published on 22 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-2175 in the wild and no public exploit code.\n\nAffected product: INFORMATION-TECHNOLOGY PROMOTION AGENCY, JAPAN (IPA) Empirical Project Monitor - eXtended. 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-2017-2175/ (Markdown: https://insights.sbomify.com/CVE-2017-2175/index.md)","id":"CVE-2017-2175","markdown":"https://insights.sbomify.com/CVE-2017-2175/index.md","name":"CVE-2017-2175","record":{"aliases":["GHSA-c2j7-mgrp-5g3p"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Project monitoring software","requires_auth":"none","summary":"Remote attackers can gain privileges and execute code by placing a malicious DLL in a directory searched by the application.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"empirical_project_monitor_-_extended","vendor":"ipa"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"Untrusted search path vulnerability in Empirical Project Monitor - eXtended all versions allows remote attackers to gain privileges via a Trojan horse DLL in an unspecified directory.","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":"Other in Empirical Project Monitor - eXtended","id":"CVE-2017-2175","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in clock 01 setup.exe","id":"CVE-2017-2176"},"packages":[],"prev":{"headline":"Cross-site scripting in Empirical Project Monitor - eXtended","id":"CVE-2017-2174"},"products":["Empirical Project Monitor - eXtended"],"published":"2017-05-22","related":[{"cvss_score":6.1,"headline":"Cross-site scripting in Empirical Project Monitor - eXtended","id":"CVE-2017-2174","kev_date_added":null,"published":"2017-05-22"},{"cvss_score":5.4,"headline":"Cross-site scripting in Empirical Project Monitor - eXtended","id":"CVE-2017-2173","kev_date_added":null,"published":"2017-05-22"}],"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-05","vendors":["INFORMATION-TECHNOLOGY PROMOTION AGENCY, JAPAN (IPA)"]},"summary":"Remote attackers can gain privileges and execute code by placing a malicious DLL in a directory searched by the application.","url":"https://insights.sbomify.com/CVE-2017-2175/"}