# CVE-2023-35619: Microsoft Outlook for Mac Spoofing Vulnerability

> Attackers can spoof content in Microsoft Outlook for Mac, potentially misleading users about the origin or nature of messages.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2023
- **Updated:** 1 Jan 2025
- **Also known as:** GHSA-xxq5-c27j-953j

## What is CVE-2023-35619?

CVE-2023-35619 is a medium-severity vulnerability in Microsoft Office Long Term Servicing Channel, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft Outlook for Mac Spoofing Vulnerability

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2023-35619?

It affects 1 product.


Products: Microsoft Office Long Term Servicing Channel.

## How do I fix CVE-2023-35619?

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

## Is CVE-2023-35619 being exploited?

There is no known exploitation of CVE-2023-35619 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35619 and fix it if it is affected.

What it is: CVE-2023-35619 is a medium-severity vulnerability in Microsoft Office Long Term Servicing Channel, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-35619 in the wild and no public exploit code.

Affected product: Microsoft Office Long Term Servicing Channel. 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-2023-35619/ (Markdown: https://insights.sbomify.com/CVE-2023-35619/index.md)
```

## Sources

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

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