{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2017-5565 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-5565 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-5565 is a medium-severity code injection vulnerability in n/a, published on 21 Mar 2017. 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-2017-5565 and fix it if it is affected.\n\nWhat it is: CVE-2017-5565 is a medium-severity code injection vulnerability in n/a, published on 21 Mar 2017. 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-2017-5565 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-2017-5565/ (Markdown: https://insights.sbomify.com/CVE-2017-5565/index.md)","id":"CVE-2017-5565","markdown":"https://insights.sbomify.com/CVE-2017-5565/index.md","name":"CVE-2017-5565","record":{"aliases":["GHSA-cm6q-r84p-pcwg"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Trend Micro Antivirus","requires_auth":"high_privilege","summary":"Local attackers can bypass self-protection to inject arbitrary code and take full control of Trend Micro processes via a DoubleAgent attack.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"antivirus\\+","vendor":"trendmicro"},{"product":"internet_security","vendor":"trendmicro"},{"product":"maximum_security","vendor":"trendmicro"},{"product":"premium_security","vendor":"trendmicro"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"Code injection vulnerability in Trend Micro Maximum Security 11.0 (and earlier), Internet Security 11.0 (and earlier), and Antivirus+ Security 11.0 (and earlier) allows a local attacker to bypass a self-protection mechanism, inject arbitrary code, and take full control of any Trend Micro process via a \"DoubleAgent\" attack. One perspective on this issue is that (1) these products do not use the Protected Processes feature, and therefore an attacker can enter an arbitrary Application Verifier Provider DLL under Image File Execution Options in the registry; (2) the self-protection mechanism is intended to block all local processes (regardless of privileges) from modifying Image File Execution Options for these products; and (3) this mechanism can be bypassed by an attacker who temporarily renames Image File Execution Options during the attack.","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 n/a","id":"CVE-2017-5565","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":0,"n_references":4,"next":{"headline":"Code injection in n/a","id":"CVE-2017-5566"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-5563"},"products":["n/a"],"published":"2017-03-21","related":[{"cvss_score":7.8,"headline":"Memory corruption in Trend Micro Maximum Security","id":"CVE-2018-6232","kev_date_added":null,"published":"2018-05-25"},{"cvss_score":7.8,"headline":"Memory corruption in Trend Micro Maximum Security","id":"CVE-2018-6233","kev_date_added":null,"published":"2018-05-25"},{"cvss_score":7.8,"headline":"Memory corruption in Trend Micro Maximum Security","id":"CVE-2018-6235","kev_date_added":null,"published":"2018-05-25"},{"cvss_score":7,"headline":"Race condition in Trend Micro Maximum Security","id":"CVE-2018-6236","kev_date_added":null,"published":"2018-05-25"},{"cvss_score":5.5,"headline":"Information disclosure in Trend Micro Maximum Security","id":"CVE-2018-6234","kev_date_added":null,"published":"2018-05-25"}],"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":["n/a"]},"summary":"Local attackers can bypass self-protection to inject arbitrary code and take full control of Trend Micro processes via a DoubleAgent attack.","url":"https://insights.sbomify.com/CVE-2017-5565/"}