Authenticated user-data disclosure via unchecked edit access
Published Aug 28, 2023 · Updated Oct 2, 2024
Improper authorization in Omeka S before 4.0.4 allows remote authenticated users to view another user's settings and API key identity. UserController::editAction retrieved and rendered the requested user before checking whether the requester was allowed to update that account. Any low-privilege account able to reach the admin user edit route can disclose settings and the identity half of another user's API keys, but cannot change the account through this flaw.
Summary
What happened
Improper authorization in Omeka S before 4.0.4 allows remote authenticated users to view another user's settings and API key identity. UserController::editAction retrieved and rendered the requested user before checking whether the requester was allowed to update that account. Any low-privilege account able to reach the admin user edit route can disclose settings and the identity half of another user's API keys, but cannot change the account through this flaw.
The record
- CVE
- CVE-2023-4560
- Published
- Aug 28, 2023
- Updated
- Oct 2, 2024
- Vendor
- Omeka
- Product
- Omeka S
- Classifications
- CWE-612, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 2023CVE publishedPublication date reported by the CVE source.
- Oct 2, 2024Record 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=0 <4.0.4
- Affected versionversion=unspecified <4.0.4
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
- IDOR in Users Edit screenproof 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