# CVE-2016-4314: WSO2 Carbon directory traversal vulnerability

> Authenticated administrators can read arbitrary files via directory traversal in the LogViewer Admin Service.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mjww-vqqw-v78q

## What is CVE-2016-4314?

CVE-2016-4314 is a medium-severity path traversal vulnerability in n/a, published on 16 Feb 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2016-4314?

2 open source packages ship an affected version, including org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui` | Maven | All versions to 4.4.5 | None |
| `org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui` | Maven | All versions to 4.4.5 | None |

Products: Wso2 Carbon.

## How do I fix CVE-2016-4314?

No fix has been published for CVE-2016-4314 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-4314 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-4314 exists.

Public exploit code:

- WSO2 Carbon 4.4.5 - Local File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-4316](https://insights.sbomify.com/CVE-2016-4316/): WSO2 Carbon vulnerable to Cross-site Scripting (medium 6.1)
- [CVE-2016-4315](https://insights.sbomify.com/CVE-2016-4315/): Cross-site request forgery in n/a (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4314 and fix it if it is affected.

What it is: CVE-2016-4314 is a medium-severity path traversal vulnerability in n/a, published on 16 Feb 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-4314 exists.

Affected packages and fixed versions:
- org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui (Maven): affected all versions up to 4.4.5; no fix listed
- org.wso2.carbon.commons:org.wso2.carbon.logging.view.ui (Maven): affected all versions up to 4.4.5; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-4314/ (Markdown: https://insights.sbomify.com/CVE-2016-4314/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-4314
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-4314
- OSV: https://osv.dev/vulnerability/CVE-2016-4314

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-4314/
Summaries are generated and may contain mistakes; the official description above is the record.