# CVE-2023-41318: Unsafe media served inline on download endpoints in matrix-media-repo

> Attackers can execute scripts via malicious SVG media served inline, requiring operators to upgrade matrix-media-repo.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-5crw-6j7v-xc72, GO-2023-2053

## What is CVE-2023-41318?

CVE-2023-41318 is a medium-severity cross-site scripting vulnerability in turt2live matrix-media-repo, published on 8 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

matrix-media-repo is a highly customizable multi-domain media repository for the Matrix chat ecosystem. In affected versions an attacker could upload a malicious piece of media to the media repo, which would then be served with `Content-Disposition: inline` upon download. This vulnerability could be leveraged to execute scripts embedded in SVG content. Commits `77ec235` and `bf8abdd` fix the issue and are included in the 1.3.0 release. Operators should upgrade to v1.3.0 as soon as possible. Operators unable to upgrade should override the `Content-Disposition` header returned by matrix-media-repo as a workaround.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

3 open source packages ship an affected version, including github.com/turt2live/matrix-media-repo. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/turt2live/matrix-media-repo` | Go | All versions | 1.3.0 |
| `github.com/turt2live/matrix-media-repo` | Go | All versions | 1.3.0 |
| `github.com/turt2live/matrix-media-repo` | Go | All versions | 1.3.0 |

Products: Turt2live Matrix-Media-Repo.

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

Upgrade github.com/turt2live/matrix-media-repo to 1.3.0 or later.

## Is CVE-2023-41318 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41318 is a medium-severity cross-site scripting vulnerability in turt2live matrix-media-repo, published on 8 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-41318 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/turt2live/matrix-media-repo (Go): affected all versions; fixed in 1.3.0
- github.com/turt2live/matrix-media-repo (Go): affected all versions; fixed in 1.3.0
- github.com/turt2live/matrix-media-repo (Go): affected all versions; fixed in 1.3.0

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

## Sources

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

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