Authenticated task forgery via trusted creator field
Published Jun 21, 2021 · Updated Aug 4, 2024
Improper authorization in White Shark System 1.3.2 allows remote authenticated users to create tasks attributed to an administrator. The default_task_add.php handler trusts the client-supplied csa_create_user field as the task dispatcher without verifying that identity. A valid session is required, and changing that field to an administrator identifier forges task authorship and alters application data.
Summary
What happened
Improper authorization in White Shark System 1.3.2 allows remote authenticated users to create tasks attributed to an administrator. The default_task_add.php handler trusts the client-supplied csa_create_user field as the task dispatcher without verifying that identity. A valid session is required, and changing that field to an administrator identifier forges task authorship and alters application data.
The record
- CVE
- CVE-2020-20467
- Published
- Jun 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-472, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
Weakness, pattern, technique
Public exploit references
- default_task_add.php forged-task HTTP requestproof 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