# CVE-2024-49193: Auth bypass in n/a

> Remote attackers can read ticket history by spoofing email Cc fields due to insufficient spoofing detection and predictable support addresses.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2024
- **Updated:** 16 Oct 2024
- **Also known as:** GHSA-vv5g-xq9c-77w7

## What is CVE-2024-49193?

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.

### Official 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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2024-49193?


## How do I fix CVE-2024-49193?

No fix has been published for CVE-2024-49193 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-49193 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49193 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49193 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-49193 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-49193/ (Markdown: https://insights.sbomify.com/CVE-2024-49193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-49193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-49193
- OSV: https://osv.dev/vulnerability/CVE-2024-49193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-49193/
Summaries are generated and may contain mistakes; the official description above is the record.