Appointment disclosure and modification via unchecked object authorization
Published Jul 9, 2024 · Updated Aug 2, 2024
Broken object-level authorization in Easy!Appointments before 1.5.0 allows remote authenticated users to read, modify, or delete any appointment. The GET, PUT, and DELETE /appointments/{appointmentId} handlers accept a caller-controlled appointment ID without verifying authorization for the referenced record. A customer, provider, or secretary account is sufficient, and successful requests expose appointment details or alter or remove the record.
Summary
What happened
Broken object-level authorization in Easy!Appointments before 1.5.0 allows remote authenticated users to read, modify, or delete any appointment. The GET, PUT, and DELETE /appointments/{appointmentId} handlers accept a caller-controlled appointment ID without verifying authorization for the referenced record. A customer, provider, or secretary account is sufficient, and successful requests expose appointment details or alter or remove the record.
The record
- CVE
- CVE-2023-38049
- Published
- Jul 9, 2024
- Updated
- Aug 2, 2024
- Vendor
- Alex Tselegidis
- Product
- Easy!Appointments
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Aug 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 <1.5.0
- Affected versionversion=* <1.5.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
- Unit 42 appointment API request demonstrationproof of concept · demonstrated
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