Authenticated code execution via unsafe YAML deserialization
Published Feb 11, 2022 · Updated Aug 4, 2024
Unsafe YAML deserialization in Magnolia CMS 6.2.3 and earlier allows remote authenticated users to execute arbitrary code via imported YAML. The SnakeYAML parser accepts application-specific type tags during CMS import and instantiates attacker-selected Java constructors. A valid CMS account and access to a YAML-capable Import function are required; successful exploitation runs code in the server process context.
Summary
What happened
Unsafe YAML deserialization in Magnolia CMS 6.2.3 and earlier allows remote authenticated users to execute arbitrary code via imported YAML. The SnakeYAML parser accepts application-specific type tags during CMS import and instantiates attacker-selected Java constructors. A valid CMS account and access to a YAML-capable Import function are required; successful exploitation runs code in the server process context.
The record
- CVE
- CVE-2021-46364
- Published
- Feb 11, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2022CVE 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
- Magnolia CMS YAML deserialization proof of conceptfunctional · 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