{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-6080 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-6080 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-6080 is a critical vulnerability in Zammad Zammad, published on 13 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-6080 and fix it if it is affected.\n\nWhat it is: CVE-2017-6080 is a critical vulnerability in Zammad Zammad, published on 13 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-6080 in the wild and no public exploit code.\n\nAffected product: Zammad Zammad. 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-6080/ (Markdown: https://insights.sbomify.com/CVE-2017-6080/index.md)","id":"CVE-2017-6080","markdown":"https://insights.sbomify.com/CVE-2017-6080/index.md","name":"CVE-2017-6080","record":{"aliases":["GHSA-7f39-jjj6-7fwv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Zammad helpdesk","requires_auth":"none","summary":"Attackers can read user data via cross-domain requests due to missing CORS protections in the Zammad REST API.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zammad","vendor":"zammad"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An issue was discovered in Zammad before 1.0.4, 1.1.x before 1.1.3, and 1.2.x before 1.2.1, caused by lack of a protection mechanism involving HTTP Access-Control headers. To exploit the vulnerability, an attacker can send cross-domain requests directly to the REST API for users with a valid session cookie and receive the result.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-6080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"zammad:zammad","products":["zammad:zammad"],"type":"csrf","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2017-6081"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2017-6079"},"products":["n/a"],"published":"2017-03-13","related":[{"cvss_score":8.7,"headline":"Zammad GmbH Zammad Session Fixation","id":"CVE-2026-102489","kev_date_added":"2026-10-02","published":"2026-09-30"},{"cvss_score":8.5,"headline":"Zammad GmbH Zammad Improper Privilege Management","id":"CVE-2026-102490","kev_date_added":"2026-10-02","published":"2026-09-30"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-48021","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2022-35490","kev_date_added":null,"published":"2022-08-08"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2021-42090","kev_date_added":null,"published":"2021-10-07"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-42094","kev_date_added":null,"published":"2021-10-07"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-26030","kev_date_added":null,"published":"2020-12-28"}],"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":"Attackers can read user data via cross-domain requests due to missing CORS protections in the Zammad REST API.","url":"https://insights.sbomify.com/CVE-2017-6080/"}