# CVE-2023-45698: HCL Sametime is impacted by clickjacking

> Attackers can perform clickjacking attacks against users of the HCL Sametime Outlook add-in due to missing security headers.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Feb 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-cv4w-8c77-w5jw

## What is CVE-2023-45698?

CVE-2023-45698 is a medium-severity vulnerability in HCL Sametime, published on 10 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Sametime is impacted by lack of clickjacking protection in Outlook add-in. The application is not implementing appropriate protections in order to protect users from clickjacking attacks.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

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

It affects 1 product.


Products: Hcltech Sametime Chat and Meetings.

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

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

## Is CVE-2023-45698 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45698 is a medium-severity vulnerability in HCL Sametime, published on 10 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-45698 in the wild and no public exploit code.

Affected product: HCL Sametime. 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-45698/ (Markdown: https://insights.sbomify.com/CVE-2023-45698/index.md)
```

## Sources

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

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