# CVE-2023-45303: ThingsBoard Server-Side Template Injection

> Attackers with email template modification rights can execute arbitrary code via Server-Side Template Injection in ThingsBoard.

- **Severity:** High 8.4 (`CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:H/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-6pgr-j9v4-xfvv

## What is CVE-2023-45303?

CVE-2023-45303 is a high-severity code injection vulnerability in n/a, published on 6 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

ThingsBoard before 3.5 allows Server-Side Template Injection if users are allowed to modify an email template, because Apache FreeMarker supports freemarker.template.utility.Execute (for content sent to the /api/admin/settings endpoint).

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

2 open source packages ship an affected version, including org.thingsboard:thingsboard. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.thingsboard:thingsboard` | Maven | All versions | 3.5 |
| `org.thingsboard:thingsboard` | Maven | All versions | 3.5 |

Products: Thingsboard Thingsboard.

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

Upgrade org.thingsboard:thingsboard to 3.5 or later.

## Is CVE-2023-45303 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-40004](https://insights.sbomify.com/CVE-2022-40004/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2022-45608](https://insights.sbomify.com/CVE-2022-45608/): Privilege escalation in n/a (high 8.8)
- [CVE-2022-48341](https://insights.sbomify.com/CVE-2022-48341/): Privilege escalation in n/a (high 8.8)
- [CVE-2020-27687](https://insights.sbomify.com/CVE-2020-27687/): Open redirect in n/a (high 8.8)
- [CVE-2023-26462](https://insights.sbomify.com/CVE-2023-26462/): Hardcoded credentials in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45303 is a high-severity code injection vulnerability in n/a, published on 6 Oct 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45303 exists.

Affected packages and fixed versions:
- org.thingsboard:thingsboard (Maven): affected all versions; fixed in 3.5
- org.thingsboard:thingsboard (Maven): affected all versions; fixed in 3.5

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-45303/ (Markdown: https://insights.sbomify.com/CVE-2023-45303/index.md)
```

## Sources

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

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