Scan-directory prediction via timestamp-derived names
Published Aug 12, 2021 · Updated Aug 4, 2024
Insufficient randomness in reNgine 0.5 and earlier allows remote attackers to predict scan-result directory names during reconnaissance. The initiate_scan function derives current_scan_dir from the target domain and a second-resolution timestamp, making the workspace name guessable. The public record does not disclose how attackers exploit that predictability or what data, execution, or service impact follows.
Summary
What happened
Insufficient randomness in reNgine 0.5 and earlier allows remote attackers to predict scan-result directory names during reconnaissance. The initiate_scan function derives current_scan_dir from the target domain and a second-resolution timestamp, making the workspace name guessable. The public record does not disclose how attackers exploit that predictability or what data, execution, or service impact follows.
The record
- CVE
- CVE-2021-38606
- Published
- Aug 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 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?
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
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