{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49193 exists.","fix":"No fix has been published for CVE-2024-49193 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-49193 is a high-severity authentication bypass vulnerability in n/a, published on 12 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-49193 and fix it if it is affected.\n\nWhat it is: CVE-2024-49193 is a high-severity authentication bypass vulnerability in n/a, published on 12 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49193 exists.\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-2024-49193/ (Markdown: https://insights.sbomify.com/CVE-2024-49193/index.md)","id":"CVE-2024-49193","markdown":"https://insights.sbomify.com/CVE-2024-49193/index.md","name":"CVE-2024-49193","record":{"aliases":["GHSA-vv5g-xq9c-77w7"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Zendesk support platform","requires_auth":"none","summary":"Remote attackers can read ticket history by spoofing email Cc fields due to insufficient spoofing detection and predictable support addresses.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"Zendesk before 2024-07-02 allows remote attackers to read ticket history via e-mail spoofing, because Cc fields are extracted from incoming e-mail messages and used to grant additional authorization for ticket viewing, the mechanism for detecting spoofed e-mail messages is insufficient, and the support e-mail addresses associated with individual tickets are predictable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2024-49193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Databricks JDBC Driver Command Injection vulnerability","id":"CVE-2024-49194"},"packages":[],"prev":{"headline":"Microsoft Update Catalog Elevation of Privilege Vulnerability","id":"CVE-2024-49147"},"products":["n/a"],"published":"2024-10-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-16","vendors":["n/a"]},"summary":"Remote attackers can read ticket history by spoofing email Cc fields due to insufficient spoofing detection and predictable support addresses.","url":"https://insights.sbomify.com/CVE-2024-49193/"}