Authenticated user-data read and modification via unchecked user_id
Published Apr 10, 2022 · Updated Aug 3, 2024
Improper access control in OFCMS 1.1.4 allows remote authenticated users to read and modify other users' personal information. The detail method in SysUserController uses a caller-controlled user_id for the user detail request without verifying that the requested record belongs to the logged-in account. Any user with back-end access can substitute another identifier, exposing and permitting changes to that account's personal data.
Summary
What happened
Improper access control in OFCMS 1.1.4 allows remote authenticated users to read and modify other users' personal information. The detail method in SysUserController uses a caller-controlled user_id for the user detail request without verifying that the requested record belongs to the logged-in account. Any user with back-end access can substitute another identifier, exposing and permitting changes to that account's personal data.
The record
- CVE
- CVE-2022-27960
- Published
- Apr 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1087
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
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
- OFCMS user_id substitution 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