Note impersonation via alias-ID collision
Published Aug 4, 2023 · Updated Oct 3, 2024
Authentication bypass in HedgeDoc 1.9.8 and earlier allows remote attackers to hide or impersonate notes through a crafted alias. The /new/ handler accepts an existing note ID as an alias without checking ID collisions, while note lookup resolves aliases before IDs. Exploitation requires freeURL mode and knowledge of the target note ID; access can be anonymous or restricted to authenticated users, and original data remains stored.
Summary
What happened
Authentication bypass in HedgeDoc 1.9.8 and earlier allows remote attackers to hide or impersonate notes through a crafted alias. The /new/ handler accepts an existing note ID as an alias without checking ID collisions, while note lookup resolves aliases before IDs. Exploitation requires freeURL mode and knowledge of the target note ID; access can be anonymous or restricted to authenticated users, and original data remains stored.
The record
- CVE
- CVE-2023-38487
- Published
- Aug 4, 2023
- Updated
- Oct 3, 2024
- Vendor
- HedgeDoc
- Product
- HedgeDoc
- Classifications
- CWE-289, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.9.9
- Affected versionversion=< 1.9.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor POST /new/<ALIAS> proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo