Cyber Resilience

CVE-2024-45308

Hedgedoc ≤ 1.10.0

Public PoC
Published
02 September 2024
Modified
22 September 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS Score 0.0055 43th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2024-45308 is a medium-severity Improper Validation of Unsafe Equivalence in Input (CWE-1289) vulnerability in Hedgedoc Hedgedoc. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

HedgeDoc is an open source, real-time, collaborative, markdown notes application. When using HedgeDoc 1 with MySQL or MariaDB, it is possible to create notes with an alias matching the ID of existing notes. The affected existing note can then not…

more

be accessed anymore and is effectively hidden by the new one. When the freeURL feature is enabled (by setting the `allowFreeURL` config option or the `CMD_ALLOW_FREEURL` environment variable to `true`), any user with the appropriate permissions can create a note with an arbitrary alias, e.g. by accessing it in the browser. When MySQL or MariaDB are used, it is possible to create a new note with an alias that matches the lower-cased ID of a different note. HedgeDoc then always presents the new note to users, as these databases perform case-insensitive matching and the lower-cased alias is found first. This issue only affects HedgeDoc instances that use MySQL or MariaDB. Depending on the permission settings of the HedgeDoc instance, the issue can be exploited only by logged-in users or by all (including non-logged-in) users. The exploit requires knowledge of the ID of the target note. Attackers could use this issue to present a manipulated copy of the original note to the user, e.g. by replacing the links with malicious ones. Attackers can also use this issue to prevent access to the original note, causing a denial of service. No data is lost, as the original content of the affected notes is still present in the database. Users are advised to upgrade to version 1.10.0 which addresses this issue. Users unable to upgrade may disable freeURL mode which prevents the exploitation of this issue. The impact can also be limited by restricting freeURL note creation to trusted, logged-in users by enabling `requireFreeURLAuthentication`/`CMD_REQUIRE_FREEURL_AUTHENTICATION`.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-38487Same product: Hedgedoc Hedgedoc
CVE-2025-32391Same product: Hedgedoc Hedgedoc
CVE-2026-25642Same product: Hedgedoc Hedgedoc
CVE-2026-3563Shared CWE-1289
CVE-2026-45191Shared CWE-1289
CVE-2026-46644Shared CWE-1289
CVE-2026-60074Shared CWE-1289
CVE-2026-27610Shared CWE-1289
CVE-2026-45190Shared CWE-1289
CVE-2026-39972Shared CWE-1289

Affected Assets

hedgedoc
hedgedoc
≤ 1.10.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.2.2
  • V9.1.3
  • V10.4.6
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 requires validity checks on information inputs, directly stopping unsafe equivalence validation failures for identifiers and references.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input validation and equivalence checking to prevent this class of flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect unsafe equivalence flaws but does not prevent them at design time.

prevents

Application security requirements can mandate input validation rules that prevent unsafe equivalence checks.

prevents

Secure architecture principles include proper input validation and canonicalization to avoid unsafe equivalence.

prevents

Secure coding standards directly require correct validation of resource identifiers and equivalence checks.

References