Unauthorized data access via client-supplied owner identifiers
Published Dec 28, 2022 · Updated Apr 10, 2025
Improper authorization in Memos 0.9.0 and earlier allows remote attackers to access or alter another user's application data. API request models accept client-supplied creator, user, and memo identifiers, while handlers fail to bind them consistently to the requester. No authentication or user interaction is required, and successful requests disclose protected records or make limited unauthorized changes.
Summary
What happened
Improper authorization in Memos 0.9.0 and earlier allows remote attackers to access or alter another user's application data. API request models accept client-supplied creator, user, and memo identifiers, while handlers fail to bind them consistently to the requester. No authentication or user interaction is required, and successful requests disclose protected records or make limited unauthorized changes.
The record
- CVE
- CVE-2022-4804
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-285, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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 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