SSRF and file truncation via unsafe deserialization
Published Mar 28, 2022 · Updated Apr 23, 2025
Deserialization of untrusted data in Orckestra C1 CMS before 6.12 allows remote authenticated users to trigger SSRF and truncate files. CompositeJsonSerializer.Deserialize accepts user-controlled serializedEntityToken values, while its binder permits internal C1 and broad .NET classes that form gadget chains. An authenticated session is required, but a crafted site can submit the GET endpoint without anti-CSRF tokens, causing internal requests or zero-length files.
Summary
What happened
Deserialization of untrusted data in Orckestra C1 CMS before 6.12 allows remote authenticated users to trigger SSRF and truncate files. CompositeJsonSerializer.Deserialize accepts user-controlled serializedEntityToken values, while its binder permits internal C1 and broad .NET classes that form gadget chains. An authenticated session is required, but a crafted site can submit the GET endpoint without anti-CSRF tokens, causing internal requests or zero-length files.
The record
- CVE
- CVE-2022-24789
- Published
- Mar 28, 2022
- Updated
- Apr 23, 2025
- Vendor
- Orckestra
- Product
- C1 CMS Foundation
- Classifications
- CWE-918, CWE-502, T1190, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.12
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
- GitHub Security Lab serializedEntityToken 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