Code execution via untrusted pickle deserialization
Published Jun 21, 2021 · Updated Aug 4, 2024
Code execution in Manuskript 0.12.0 and earlier allows attackers to run arbitrary code by opening a crafted project file. When the project loader reads embedded settings.pickle data, settings.py passes attacker-controlled bytes to pickle.load(), which reconstructs executable Python objects without validation. A user must open an untrusted project; the maintainer disputes the issue because the product is not intended to open untrusted projects.
Summary
What happened
Code execution in Manuskript 0.12.0 and earlier allows attackers to run arbitrary code by opening a crafted project file. When the project loader reads embedded settings.pickle data, settings.py passes attacker-controlled bytes to pickle.load(), which reconstructs executable Python objects without validation. A user must open an untrusted project; the maintainer disputes the issue because the product is not intended to open untrusted projects.
The record
- CVE
- CVE-2021-35196
- Published
- Jun 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Theologeek
- Product
- Manuskript
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.12.0
What conditions does exploitation require?
What is affected?
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
- Arbitrary Code Execution in Manuskript 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