{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-2208 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-2208 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-2208 is a high-severity code injection vulnerability in Acquisition, Technology \u0026 Logistics Agency Installer of electronic tendering and bid opening system, published on 7 Jul 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-2208 and fix it if it is affected.\n\nWhat it is: CVE-2017-2208 is a high-severity code injection vulnerability in Acquisition, Technology \u0026 Logistics Agency Installer of electronic tendering and bid opening system, published on 7 Jul 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-2208 in the wild and no public exploit code.\n\nAffected product: Acquisition, Technology \u0026 Logistics Agency Installer of electronic tendering and bid opening system. 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-2208/ (Markdown: https://insights.sbomify.com/CVE-2017-2208/index.md)","id":"CVE-2017-2208","markdown":"https://insights.sbomify.com/CVE-2017-2208/index.md","name":"CVE-2017-2208","record":{"aliases":["GHSA-m52f-r8pr-rgrx"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tendering system installer","requires_auth":"none","summary":"An attacker can execute arbitrary code by placing a malicious executable in a directory searched by the tendering system installer.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"installer_of_electronic_tendering","vendor":"acquisition_technology_and_logistics_agency"}],"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 Installer of Electronic tendering and bid opening system available prior to June 12, 2017 allows an attacker to execute arbitrary code via a specially crafted executable file 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":"Code injection in Installer of electronic tendering and bid opening system","id":"CVE-2017-2208","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Installer of Houkokusyo Sakusei Shien Tool","id":"CVE-2017-2209"},"packages":[],"prev":{"headline":"Privilege escalation in The installer of SaAT Personal","id":"CVE-2017-2207"},"products":["Installer of electronic tendering and bid opening system"],"published":"2017-07-07","related":[],"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":["Acquisition, Technology \u0026 Logistics Agency"]},"summary":"An attacker can execute arbitrary code by placing a malicious executable in a directory searched by the tendering system installer.","url":"https://insights.sbomify.com/CVE-2017-2208/"}