{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8387 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8387 is a medium-severity memory corruption vulnerability in Stdutility Stdu Viewer, published on 5 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-8387 and fix it if it is affected.\n\nWhat it is: CVE-2017-8387 is a medium-severity memory corruption vulnerability in Stdutility Stdu Viewer, published on 5 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-8387 in the wild and no public exploit code.\n\nAffected product: Stdutility Stdu Viewer. 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-8387/ (Markdown: https://insights.sbomify.com/CVE-2017-8387/index.md)","id":"CVE-2017-8387","markdown":"https://insights.sbomify.com/CVE-2017-8387/index.md","name":"CVE-2017-8387","record":{"aliases":["GHSA-286j-65v5-3w84"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"STDU Viewer","requires_auth":"none","summary":"User-assisted attackers can execute arbitrary code via a crafted file in STDU Viewer, requiring victim interaction with specific commands.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"stdu_viewer","vendor":"stdutility"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"STDU Viewer version 1.6.375 might allow user-assisted attackers to execute code via a crafted file. One threat model is a victim who obtains an untrusted crafted file from a remote location and issues several user-defined commands including Ctrl-+ commands.","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":"Memory corruption in n/a","id":"CVE-2017-8387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"stdutility:stdu_viewer","products":["stdutility:stdu_viewer"],"type":"memory_corruption","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"GeniXCMS Mailbox validation logic vulnerability","id":"CVE-2017-8388"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2017-8386"},"products":["n/a"],"published":"2017-07-05","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14688","kev_date_added":null,"published":"2017-09-22"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14689","kev_date_added":null,"published":"2017-09-22"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14690","kev_date_added":null,"published":"2017-09-22"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14691","kev_date_added":null,"published":"2017-09-22"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14692","kev_date_added":null,"published":"2017-09-22"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14542","kev_date_added":null,"published":"2017-09-18"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2017-14543","kev_date_added":null,"published":"2017-09-18"}],"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":"User-assisted attackers can execute arbitrary code via a crafted file in STDU Viewer, requiring victim interaction with specific commands.","url":"https://insights.sbomify.com/CVE-2017-8387/"}