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

> Remote attackers can write arbitrary files via directory traversal in SolidWorks Workgroup PDM file uploads.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h2q9-p4wq-924f

## What is CVE-2014-100015?

CVE-2014-100015 is a medium-severity path traversal vulnerability in n/a, published on 13 Jan 2015. It can be exploited over the network, with no action from the victim.

### Official description

Directory traversal vulnerability in pdmwService.exe in SolidWorks Workgroup PDM 2014 allows remote attackers to write to arbitrary files via a .. (dot dot) in the filename in a file upload.

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

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

It affects 1 product.


Products: Solidworks Product Data Management.

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

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

## Is CVE-2014-100015 being exploited?

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

Public exploit code:

- SolidWorks Workgroup PDM 2014 SP2 - Arbitrary File Write (exploitdb)
- SolidWorks Workgroup PDM 2014 pdmwService.exe Arbitrary File Write (metasploit)
- SolidWorks Workgroup PDM 2014 - 'pdmwService.exe' Arbitrary File Write (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-100014](https://insights.sbomify.com/CVE-2014-100014/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-100015 is a medium-severity path traversal vulnerability in n/a, published on 13 Jan 2015. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2014-100015 exists.

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

## Sources

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

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