Memo archiving via missing ownership validation
Published Dec 28, 2022 · Updated Apr 10, 2025
Access control bypass in Memos 0.9.0 and earlier allows remote authenticated users to archive other users' memos via memo IDs. The PATCH /api/memo/:memoId handler looked up the requested memo without reliably enforcing creator ownership before applying rowStatus changes. A valid account and another memo's numeric ID were sufficient to move that memo into the archived state without deleting its stored content.
Summary
What happened
Access control bypass in Memos 0.9.0 and earlier allows remote authenticated users to archive other users' memos via memo IDs. The PATCH /api/memo/:memoId handler looked up the requested memo without reliably enforcing creator ownership before applying rowStatus changes. A valid account and another memo's numeric ID were sufficient to move that memo into the archived state without deleting its stored content.
The record
- CVE
- CVE-2022-4814
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-284, T1565.001
- 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
- huntr.dev memo-archiving proof of conceptproof of concept · unverified
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