# CVE-2014-3777: Path traversal in n/a

> Remote attackers can read arbitrary files via directory traversal in the xmlin parameter of Reportico PHP Report Designer.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mh5v-7j2w-5pmh

## What is CVE-2014-3777?

CVE-2014-3777 is a medium-severity path traversal vulnerability in n/a, published on 16 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory traversal vulnerability in Reportico PHP Report Designer before 4.0 allows remote attackers to read arbitrary files via a .. (dot dot) in the xmlin parameter.

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

## Which versions are affected by CVE-2014-3777?

It affects 1 product.


Products: Reportico Php Report Designer.

## How do I fix CVE-2014-3777?

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

## Is CVE-2014-3777 being exploited?

There is no known exploitation of CVE-2014-3777 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3777 and fix it if it is affected.

What it is: CVE-2014-3777 is a medium-severity path traversal vulnerability in n/a, published on 16 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3777 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2014-3777/ (Markdown: https://insights.sbomify.com/CVE-2014-3777/index.md)
```

## Sources

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

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