{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5789 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-5789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-5789 is a high-severity vulnerability in n/a, published on 13 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2016-5789 and fix it if it is affected.\n\nWhat it is: CVE-2016-5789 is a high-severity vulnerability in n/a, published on 13 Oct 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2016-5789 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-2016-5789/ (Markdown: https://insights.sbomify.com/CVE-2016-5789/index.md)","id":"CVE-2016-5789","markdown":"https://insights.sbomify.com/CVE-2016-5789/index.md","name":"CVE-2016-5789","record":{"aliases":["GHSA-6r3v-mvwf-3vhh"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JanTek JTC-200","requires_auth":"low_privilege","summary":"An attacker can perform actions with victim permissions via CSRF in JanTek JTC-200, requiring user interaction.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"jtc-200_firmware","vendor":"jantek"}],"cvss":{"score":8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A Cross-site Request Forgery issue was discovered in JanTek JTC-200, all versions. An attacker could perform actions with the same permissions as a victim user, provided the victim has an active session and is induced to trigger the malicious request.","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":"Cross-site request forgery in n/a","id":"CVE-2016-5789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2016"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in n/a","id":"CVE-2016-5790"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2016-5788"},"products":["n/a"],"published":"2017-10-13","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2016-5791","kev_date_added":null,"published":"2017-10-13"}],"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-06","vendors":["n/a"]},"summary":"An attacker can perform actions with victim permissions via CSRF in JanTek JTC-200, requiring user interaction.","url":"https://insights.sbomify.com/CVE-2016-5789/"}