CVE-2026-3064
Command Injection in HummerRisk Cloud Task Scheduler (ResourceCreateService
Publication date: 2026-02-24
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| hummerrisk | hummerrisk | to 1.5.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-3064 is a critical command injection vulnerability in HummerRisk versions up to 1.5.0, specifically in the Cloud Task Scheduler component within the file ResourceCreateService.java.
The vulnerability arises from improper handling of the argument regionId, which is accepted via a REST API endpoint and stored unsanitized in the database. During task cleanup, this regionId is concatenated directly into shell commands executed on the server without proper input validation or sanitization.
This allows attackers with permission to create cloud scanning tasks to inject arbitrary operating system commands using shell metacharacters, leading to remote code execution (RCE) on the HummerRisk server with the privileges of the hummer-risk user.
The vulnerability is classified under CWE-77 and CWE-78, indicating unsafe command construction and execution based on externally influenced input. Exploitation techniques include injecting reverse shells, data exfiltration commands, arbitrary file deletion, and web shell uploads.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including remote code execution on the affected server, allowing attackers to execute arbitrary commands with the privileges of the hummer-risk user.
- Data exfiltration of sensitive information.
- Arbitrary file deletion, including critical system files via path traversal.
- Persistence through backdoors or web shells, enabling long-term unauthorized access.
- Lateral movement within internal networks and cloud infrastructure.
- Potential privilege escalation to root if sudo is configured.
- Full compromise of cloud scanning infrastructure and associated cloud resources.
Overall, the vulnerability threatens confidentiality, integrity, and availability of the affected systems and data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
[{'type': 'paragraph', 'content': 'The vulnerability can lead to data breaches and unauthorized access to sensitive information, which directly impacts compliance with regulations such as GDPR, HIPAA, PCI DSS, and SOC 2.'}, {'type': 'paragraph', 'content': "Exploitation may result in exposure of personal data, loss of data integrity, and disruption of services, all of which are violations of these standards' requirements for data protection, confidentiality, and availability."}, {'type': 'paragraph', 'content': 'Organizations using affected versions of HummerRisk may face legal and regulatory consequences if this vulnerability is exploited and leads to non-compliance.'}] [3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'Detection and monitoring of this vulnerability involve monitoring for suspicious regionId values containing shell metacharacters or command keywords.'}, {'type': 'paragraph', 'content': 'You should monitor logs for unusual command patterns such as rm -rf with unexpected paths, reverse shell indicators, or data exfiltration commands.'}, {'type': 'paragraph', 'content': 'A Sigma detection rule is available to identify potential command injection attempts via the regionId parameter.'}, {'type': 'paragraph', 'content': 'Specifically, you can check database entries for regionId values containing characters like ;, &&, |, or suspicious payloads.'}, {'type': 'paragraph', 'content': 'Commands to detect suspicious inputs might include searching logs or database entries for these patterns, for example using grep:'}, {'type': 'list_item', 'content': 'grep -rE ";|&&|\\||\\$|\\(|\\)" /path/to/logs'}, {'type': 'list_item', 'content': 'SELECT * FROM cloud_task_item WHERE region_id REGEXP \'[;&|$()<>*?\\[\\]{}"\\\'\\\\]\''}, {'type': 'paragraph', 'content': 'Additionally, monitoring for unexpected network connections or reverse shell activity on the server may help detect exploitation attempts.'}] [3]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include strict input validation on the regionId parameter to allow only valid region formats and block dangerous characters such as ;, &, |, $, (, ), <, >, *, ?, [, ], {, }, \', and ".'}, {'type': 'paragraph', 'content': "Replace unsafe shell command executions with safe Java APIs for file operations, such as Apache Commons IO's FileUtils.deleteDirectory() or Java NIO's Files.walk(), avoiding shell invocation."}, {'type': 'paragraph', 'content': 'Implement whitelisting of valid region IDs per cloud provider to reject invalid or malicious inputs.'}, {'type': 'paragraph', 'content': 'Validate paths to prevent path traversal by ensuring constructed paths remain within expected base directories.'}, {'type': 'paragraph', 'content': 'Consider replacing the affected product with an alternative, as no vendor mitigations have been provided.'}, {'type': 'paragraph', 'content': 'In the short term, monitor for suspicious inputs and commands, deploy WAF rules if possible, enforce least privilege principles, and conduct audit logging.'}] [3, 1]