Authenticated data access via user-controlled object IDs
Published Dec 28, 2022 · Updated Apr 10, 2025
Authorization bypass in Memos before 0.9.1 allows remote authenticated users to read or alter other users' data through crafted API requests. The vulnerable API request structures accepted caller-supplied CreatorID, UserID, and MemoID fields, allowing object ownership and target records to be selected without proper authorization; the fix removes those fields from JSON binding. A valid account is required, and the consequence is unauthorized disclosure or modification of Memos data rather than an unauthenticated compromise.
Summary
What happened
Authorization bypass in Memos before 0.9.1 allows remote authenticated users to read or alter other users' data through crafted API requests. The vulnerable API request structures accepted caller-supplied CreatorID, UserID, and MemoID fields, allowing object ownership and target records to be selected without proper authorization; the fix removes those fields from JSON binding. A valid account is required, and the consequence is unauthorized disclosure or modification of Memos data rather than an unauthenticated compromise.
The record
- CVE
- CVE-2022-4803
- Published
- Dec 28, 2022
- Updated
- Apr 10, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-639, T1190
- 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.dev CVE-2022-4803 bounty exploitproof 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