Arbitrary file writes via unsafe YAML deserialization
Published Dec 16, 2024 · Updated Dec 17, 2024
Deserialization of untrusted data in PlexTrac Runbooks 1.61.3 through 2.8.0 allows remote authenticated users to write arbitrary files. Runbooks import processing passes attacker-supplied YAML to an unsafe deserializer that constructs objects instead of restricting the document to inert data. Exploitation requires a low-privileged account and active user interaction, and the documented consequence is file modification rather than service interruption.
Summary
What happened
Deserialization of untrusted data in PlexTrac Runbooks 1.61.3 through 2.8.0 allows remote authenticated users to write arbitrary files. Runbooks import processing passes attacker-supplied YAML to an unsafe deserializer that constructs objects instead of restricting the document to inert data. Exploitation requires a low-privileged account and active user interaction, and the documented consequence is file modification rather than service interruption.
The record
- CVE
- CVE-2024-12687
- Published
- Dec 16, 2024
- Updated
- Dec 17, 2024
- Vendor
- PlexTrac
- Product
- PlexTrac
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 16, 2024CVE publishedPublication date reported by the CVE source.
- Dec 17, 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=1.61.3 <2.8.1
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
No public exploit references are available in this record.
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