Unauthenticated code execution via unsafe YAML deserialization
Published Mar 7, 2024 · Updated Aug 12, 2024
Unsafe deserialization in NAVER Corporation nGrinder before 3.5.9 allows remote attackers to execute code through a crafted YAML request. The unauthenticated /script/api/github/validate endpoint passes the request body's YAML content to SnakeYAML's vulnerable-by-default Yaml.loadAll sink. No account or user interaction is required, and a crafted object graph executes commands with the privileges of the nGrinder controller process.
Summary
What happened
Unsafe deserialization in NAVER Corporation nGrinder before 3.5.9 allows remote attackers to execute code through a crafted YAML request. The unauthenticated /script/api/github/validate endpoint passes the request body's YAML content to SnakeYAML's vulnerable-by-default Yaml.loadAll sink. No account or user interaction is required, and a crafted object graph executes commands with the privileges of the nGrinder controller process.
The record
- CVE
- CVE-2024-28212
- Published
- Mar 7, 2024
- Updated
- Aug 12, 2024
- Vendor
- NAVER Corporation
- Product
- nGrinder
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2024CVE publishedPublication date reported by the CVE source.
- Aug 12, 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 <3.5.9
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 crafted YAML 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