Unauthenticated code execution via SPOOLDIR injection
Published May 29, 2021 · Updated Aug 3, 2024
Code injection in the VoIPmonitor web UI before 24.61 allows remote attackers to execute arbitrary code through the recheck option. The recheck handler accepts the user-controlled SPOOLDIR value and writes it into config/configuration.php without neutralizing embedded PHP code. No authentication or user interaction is required when the web UI is network-accessible, and injected PHP runs on the affected server.
Summary
What happened
Code injection in the VoIPmonitor web UI before 24.61 allows remote attackers to execute arbitrary code through the recheck option. The recheck handler accepts the user-controlled SPOOLDIR value and writes it into config/configuration.php without neutralizing embedded PHP code. No authentication or user interaction is required when the web UI is network-accessible, and injected PHP runs on the affected server.
The record
- CVE
- CVE-2021-30461
- Published
- May 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1059
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 29, 2021CVE 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
- Al1ex CVE-2021-30461 proof of conceptproof of concept · unverified
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