CVE-2016-4314 — org.wso2.carbon.logging.v…
MEDIUMCVE-2016-4314 is a medium-severity (CVSS 4.9) Path Traversal vulnerability in org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
WSO2 Carbon directory traversal vulnerability
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.wso2.carbon.commons:org.wso2.carbon.logging.view.uiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Directory traversal vulnerability in the LogViewer Admin Service in WSO2 Carbon 4.4.5 allows remote authenticated administrators to read arbitrary files via a .. (dot dot) in the logFile parameter to downloadgz-ajaxprocessor.jsp.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui | all versions | No fix |
Affected Products
carbonwso2Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
WSO2 Carbon 4.4.5 - Local File Inclusion
by hyp3rlinx · Aug 16, 2016
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui for CVE-2016-4314. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2016-4314 in your dependencies?
Find it across Maven, including transitive dependencies.