Authorization bypass via JSON-decoded patch IDs
Published Dec 23, 2022 · Updated Apr 9, 2025
Authorization bypass in Memos before 0.9.0 allows remote attackers to alter records through object IDs in patch request bodies. Patch model ID fields were JSON-decodable, so a body-supplied ID could replace the route-selected record identifier after authorization. No authentication or user interaction is required, and successful requests can expose or modify data and interrupt service.
Summary
What happened
Authorization bypass in Memos before 0.9.0 allows remote attackers to alter records through object IDs in patch request bodies. Patch model ID fields were JSON-decodable, so a body-supplied ID could replace the route-selected record identifier after authorization. No authentication or user interaction is required, and successful requests can expose or modify data and interrupt service.
The record
- CVE
- CVE-2022-4686
- Published
- Dec 23, 2022
- Updated
- Apr 9, 2025
- Vendor
- Memos
- Product
- Memos
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 proof of concept for CVE-2022-4686proof 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