# CVE-2022-24837: Enumerable upload file names in hedgedoc

> Attackers can enumerate uploaded image filenames to leak private document contents in HedgeDoc, requiring an upgrade to fix.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-q6vv-2q26-j7rx

## What is CVE-2022-24837?

CVE-2022-24837 is a medium-severity vulnerability in hedgedoc, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HedgeDoc is an open-source, web-based, self-hosted, collaborative markdown editor. Images uploaded with HedgeDoc version 1.9.1 and later have an enumerable filename after the upload, resulting in potential information leakage of uploaded documents. This is especially relevant for private notes and affects all upload backends, except Lutim and imgur. This issue is patched in version 1.9.3 by replacing the filename generation with UUIDv4. If you cannot upgrade to HedgeDoc 1.9.3, it is possible to block POST requests to `/uploadimage`, which will disable future uploads.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-24837?

It affects 1 product.


Products: Hedgedoc Hedgedoc.

## How do I fix CVE-2022-24837?

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

## Is CVE-2022-24837 being exploited?

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

## Other vulnerabilities in hedgedoc

- [CVE-2021-29475](https://insights.sbomify.com/CVE-2021-29475/): PDF export allows arbitrary file reads (critical 10.0)
- [CVE-2020-26287](https://insights.sbomify.com/CVE-2020-26287/): Stored XSS in mermaid diagrams (high 8.7)
- [CVE-2021-39175](https://insights.sbomify.com/CVE-2021-39175/): XSS vector in slide mode speaker-view (high 8.1)
- [CVE-2021-29503](https://insights.sbomify.com/CVE-2021-29503/): Improper Neutralization of Script-Related HTML Tags in Notes (high 8.1)
- [CVE-2020-26286](https://insights.sbomify.com/CVE-2020-26286/): Arbitary file upload (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24837 and fix it if it is affected.

What it is: CVE-2022-24837 is a medium-severity vulnerability in hedgedoc, published on 11 Apr 2022. 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-2022-24837 in the wild and no public exploit code.

Affected product: hedgedoc. 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-2022-24837/ (Markdown: https://insights.sbomify.com/CVE-2022-24837/index.md)
```

## Sources

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

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