Authenticated code execution via unsanitized conf.php write
Published Feb 10, 2020 · Updated Aug 6, 2024
Code injection in Sphider before 1.3.6 allows remote authenticated users to execute arbitrary code through the administration interface. The vulnerable path fails to sanitize attacker-controlled configuration data before fwrite persists it as executable PHP in conf.php. An authenticated session and write access by the web process to conf.php are required; injected code runs with that process's privileges.
Summary
What happened
Code injection in Sphider before 1.3.6 allows remote authenticated users to execute arbitrary code through the administration interface. The vulnerable path fails to sanitize attacker-controlled configuration data before fwrite persists it as executable PHP in conf.php. An authenticated session and write access by the web process to conf.php are required; injected code runs with that process's privileges.
The record
- CVE
- CVE-2014-5083
- Published
- Feb 10, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, T1059
- 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 Command Execution / SQL Injectionproof 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