Authenticated private memo disclosure via URL identifier
Published Dec 28, 2022 · Updated Apr 10, 2025
Improper authorization in Memos before 0.9.1 allows remote authenticated users to read another user’s private memo by changing its URL ID. The memo editing route resolves the URL-supplied memo identifier without reliably binding the requested record to the signed-in owner. A signed-in account and another user’s memo identifier are required; the documented consequence is disclosure of private memo content.
Summary
What happened
Improper authorization in Memos before 0.9.1 allows remote authenticated users to read another user’s private memo by changing its URL ID. The memo editing route resolves the URL-supplied memo identifier without reliably binding the requested record to the signed-in owner. A signed-in account and another user’s memo identifier are required; the documented consequence is disclosure of private memo content.
The record
- CVE
- CVE-2022-4811
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-639, T1213
- 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.
Weakness, pattern, technique
Public exploit references
- Huntr private-memo access 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