# CVE-2014-3699: Deserialization in eDeploy

> Attackers can execute arbitrary code on eDeploy servers by sending malicious serialized data, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2vfh-w2hp-mr2m

## What is CVE-2014-3699?

CVE-2014-3699 is a critical unsafe deserialization vulnerability in eDeploy, published on 15 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

eDeploy has RCE via cPickle deserialization of untrusted data

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 2 products.


Products: Redhat Edeploy, Redhat Jboss Enterprise Web Server.

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

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

## Is CVE-2014-3699 being exploited?

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

## Other vulnerabilities in eDeploy

- [CVE-2014-3700](https://insights.sbomify.com/CVE-2014-3700/): Code injection in eDeploy (critical 9.8)
- [CVE-2014-8174](https://insights.sbomify.com/CVE-2014-8174/): Code injection in n/a (critical 9.8)
- [CVE-2014-3702](https://insights.sbomify.com/CVE-2014-3702/): Path traversal in n/a (critical 9.1)
- [CVE-2014-3701](https://insights.sbomify.com/CVE-2014-3701/): Race condition in eDeploy (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-3699 is a critical unsafe deserialization vulnerability in eDeploy, published on 15 Dec 2019. 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-3699 in the wild and no public exploit code.

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

## Sources

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

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