Path disclosure via array parameter error
Published Feb 8, 2021 · Updated Aug 3, 2024
Path disclosure in emlog 5.3.1 allows remote attackers to reveal the webroot path via a crafted request to t/index.php. The endpoint passes an array-valued action parameter to addslashes(), which expects a string and emits an error containing the server filesystem path. No authentication or user interaction is required; the disclosure primarily enables follow-on attacks that need the application path.
Summary
What happened
Path disclosure in emlog 5.3.1 allows remote attackers to reveal the webroot path via a crafted request to t/index.php. The endpoint passes an array-valued action parameter to addslashes(), which expects a string and emits an error containing the server filesystem path. No authentication or user interaction is required; the disclosure primarily enables follow-on attacks that need the application path.
The record
- CVE
- CVE-2021-3293
- Published
- Feb 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1083
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 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
- emlog v5.3.1 Full Path Disclosure 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