Remote code execution via unfiltered YAML configuration
Published May 20, 2022 · Updated Aug 3, 2024
OS command injection in reNgine 1.0.2 allows remote attackers to execute arbitrary commands through crafted YAML scan configuration. The YAML engine accepts writable configuration values without validation or filtering and passes them directly to an os.system call. Triggering the dirsearch path requires completion of the default subdomain scan first; commands run with the reNgine service's permissions.
Summary
What happened
OS command injection in reNgine 1.0.2 allows remote attackers to execute arbitrary commands through crafted YAML scan configuration. The YAML engine accepts writable configuration values without validation or filtering and passes them directly to an os.system call. Triggering the dirsearch path requires completion of the default subdomain scan first; commands run with the reNgine service's permissions.
The record
- CVE
- CVE-2022-28995
- Published
- May 20, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1059.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- YAML configuration RCE 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