# CVE-2014-100014: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in SolidWorks Workgroup PDM server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-36wg-g5hr-xh2j

## What is CVE-2014-100014?

CVE-2014-100014 is a high-severity memory corruption vulnerability in n/a, published on 13 Jan 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in pdmwService.exe in SolidWorks Workgroup PDM 2014 SP2 allow remote attackers to execute arbitrary code via a long string in a (1) 2001, (2) 2002, or (3) 2003 opcode to port 3000.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Solidworks Product Data Management.

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

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

## Is CVE-2014-100014 being exploited?

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

Public exploit code:

- SolidWorks Workgroup PDM 2014 SP2 Opcode 2001 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-100015](https://insights.sbomify.com/CVE-2014-100015/): Path traversal in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-100014 is a high-severity memory corruption vulnerability in n/a, published on 13 Jan 2015. 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-100014 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-100014/ (Markdown: https://insights.sbomify.com/CVE-2014-100014/index.md)
```

## Sources

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

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