Authenticated code execution via unsanitized settings write
Published Feb 10, 2020 · Updated Aug 6, 2024
Code injection in Sphider Pro 3.2 allows remote authenticated users to execute arbitrary PHP through crafted crawler settings. The settings-saving code passes user-controlled configuration values to fwrite without sanitization, causing PHP content to be stored in a configuration file. Administrative access is required, and successful exploitation runs attacker-supplied PHP with the web application's privileges.
Summary
What happened
Code injection in Sphider Pro 3.2 allows remote authenticated users to execute arbitrary PHP through crafted crawler settings. The settings-saving code passes user-controlled configuration values to fwrite without sanitization, causing PHP content to be stored in a configuration file. Administrative access is required, and successful exploitation runs attacker-supplied PHP with the web application's privileges.
The record
- CVE
- CVE-2014-5084
- Published
- Feb 10, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, T1505.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
- Sphider Search Engine - Multiple Vulnerabilitiesproof 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