Cross-user memo modification via request-body ID override
Published Dec 23, 2022 · Updated Apr 9, 2025
Improper access control in Memos before 0.9.0 allows remote authenticated users to edit private memos owned by other users. MemoPatch decodes the request-body ID and uses that value for the update, allowing it to override the memo identifier selected by the route. Any signed-in user who obtains another memo ID can alter that memo's stored content; the public record does not show unauthenticated access.
Summary
What happened
Improper access control in Memos before 0.9.0 allows remote authenticated users to edit private memos owned by other users. MemoPatch decodes the request-body ID and uses that value for the update, allowing it to override the memo identifier selected by the route. Any signed-in user who obtains another memo ID can alter that memo's stored content; the public record does not show unauthenticated access.
The record
- CVE
- CVE-2022-4684
- Published
- Dec 23, 2022
- Updated
- Apr 9, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 9, 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.0
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
- Cross-user private memo edit 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