Unauthorized data access via direct function requests
Published May 2, 2023 · Updated Jan 30, 2025
Authorization flaw in evasys before 8.2 Build 2286 and 9.x before 9.0 Build 2401 allows remote authenticated users to read or write unauthorized data. Server-side authorization is not enforced when privileged component URLs are requested directly or another user's object identifier is substituted. A valid trainer or subarea-administrator session is sufficient to view questionnaires and documents or rename another user's online template.
Summary
What happened
Authorization flaw in evasys before 8.2 Build 2286 and 9.x before 9.0 Build 2401 allows remote authenticated users to read or write unauthorized data. Server-side authorization is not enforced when privileged component URLs are requested directly or another user's object identifier is substituted. A valid trainer or subarea-administrator session is sufficient to view questionnaires and documents or rename another user's online template.
The record
- CVE
- CVE-2023-31435
- Published
- May 2, 2023
- Updated
- Jan 30, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2023CVE publishedPublication date reported by the CVE source.
- Jan 30, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Authorization bypass proof of conceptproof 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