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

> Attackers can access files outside the intended directory via DBD::File drivers in the Perl DBI module, leading to unauthorized data access or modification.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2020
- **Updated:** 6 Aug 2024
- **Also known as:** ALPINE-CVE-2014-10402, AZL-41925, DEBIAN-CVE-2014-10402, DLA-3035-1, GHSA-qc7v-jjp2-38r9, MGASA-2021-0451, OESA-2022-1641, UBUNTU-CVE-2014-10402

## What is CVE-2014-10402?

CVE-2014-10402 is a medium-severity path traversal vulnerability in n/a, published on 16 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the DBI module through 1.643 for Perl. DBD::File drivers can open files from folders other than those specifically passed via the f_dir attribute in the data source name (DSN). NOTE: this issue exists because of an incomplete fix for CVE-2014-10401.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Perl Dbi.

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

Upgrade to a fixed version.

## Is CVE-2014-10402 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-14739](https://insights.sbomify.com/CVE-2026-14739/): Memory corruption in DBI (critical 9.8)
- [CVE-2026-10879](https://insights.sbomify.com/CVE-2026-10879/): DBI versions before 1.648 for Perl have a heap overflow when preparsing SQL statements with more than 9 binders (critical 9.8)
- [CVE-2026-14740](https://insights.sbomify.com/CVE-2026-14740/): DBI versions before 1.650 for Perl read one byte out-of-bounds in preparse when deleting an initial SQL comment (critical 9.1)
- [CVE-2026-14380](https://insights.sbomify.com/CVE-2026-14380/): DBI versions before 1.650 for Perl are vulnerable to code injection via caller-influenced Profile (high 8.8)
- [CVE-2026-9698](https://insights.sbomify.com/CVE-2026-9698/): DBI versions before 1.648 for Perl saved errors in a limited-sized buffer (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-10402 is a medium-severity path traversal vulnerability in n/a, published on 16 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-10402 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-10402/ (Markdown: https://insights.sbomify.com/CVE-2014-10402/index.md)
```

## Sources

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

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