{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-5943 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-5943 is a high-severity vulnerability in n/a, published on 3 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-5943 and fix it if it is affected.\n\nWhat it is: CVE-2017-5943 is a high-severity vulnerability in n/a, published on 3 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-5943 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-5943/ (Markdown: https://insights.sbomify.com/CVE-2017-5943/index.md)","id":"CVE-2017-5943","markdown":"https://insights.sbomify.com/CVE-2017-5943/index.md","name":"CVE-2017-5943","record":{"aliases":["DEBIAN-CVE-2017-5943","GHSA-7p4g-wg5g-j4v4","UBUNTU-CVE-2017-5943"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Request Tracker","requires_auth":"none","summary":"Remote attackers can obtain sensitive CSRF verification tokens via a crafted URL in Request Tracker, potentially aiding further attacks.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"request_tracker","vendor":"bestpractical"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Request Tracker (RT) 4.x before 4.0.25, 4.2.x before 4.2.14, and 4.4.x before 4.4.2 allows remote attackers to obtain sensitive information about cross-site request forgery (CSRF) verification tokens via a crafted URL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2017-5943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2017-5944"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-5942"},"products":["n/a"],"published":"2017-07-03","related":[{"cvss_score":9.1,"headline":"RT: Privilege escalation and information disclosure via REST 2.0 user collection endpoint","id":"CVE-2026-44231","kev_date_added":null,"published":"2026-07-20"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2017-5944","kev_date_added":null,"published":"2017-07-03"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-41259","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-41260","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2023-45024","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-38562","kev_date_added":null,"published":"2021-10-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":"Remote attackers can obtain sensitive CSRF verification tokens via a crafted URL in Request Tracker, potentially aiding further attacks.","url":"https://insights.sbomify.com/CVE-2017-5943/"}