Cross-account post archival via missing ownership check
Published Dec 28, 2022 · Updated Apr 10, 2025
Authorization bypass in Memos before 0.9.1 allows remote authenticated users to archive any user's public or private post. The DELETE /api/memo/:memoId handler trusts an insufficient store lookup instead of explicitly confirming that the session user owns the selected memo. Any signed-in member who knows or guesses a memo identifier can alter another user's post state, including for private posts.
Summary
What happened
Authorization bypass in Memos before 0.9.1 allows remote authenticated users to archive any user's public or private post. The DELETE /api/memo/:memoId handler trusts an insufficient store lookup instead of explicitly confirming that the session user owns the selected memo. Any signed-in member who knows or guesses a memo identifier can alter another user's post state, including for private posts.
The record
- CVE
- CVE-2022-4801
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-1220, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record 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=unspecified <0.9.1
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
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