# CVE-2023-33955: Minio console object names with RIGHT-TO-LEFT OVERRIDE unicode character can be exploited

> Attackers can use Unicode characters to mask filenames in the MinIO Console, potentially misleading users about file contents.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-jv3f-7m33-qp65

## What is CVE-2023-33955?

CVE-2023-33955 is a medium-severity vulnerability in minio console, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Minio Console is the UI for MinIO Object Storage. Unicode RIGHT-TO-LEFT OVERRIDE characters can be used to mask the original filename. This issue has been patched in version 0.28.0.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

2 open source packages ship an affected version, including github.com/minio/console. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/minio/console` | Go | All versions | 0.28.0 |
| `github.com/minio/console` | Go | All versions | 0.28.0 |

Products: Minio Console.

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

Upgrade github.com/minio/console to 0.28.0 or later.

## Is CVE-2023-33955 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33955 is a medium-severity vulnerability in minio console, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33955 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/minio/console (Go): affected all versions; fixed in 0.28.0
- github.com/minio/console (Go): affected all versions; fixed in 0.28.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-33955/ (Markdown: https://insights.sbomify.com/CVE-2023-33955/index.md)
```

## Sources

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

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