# CVE-2014-0629: Privilege escalation in n/a

> Remote authenticated users can gain privileges and access sensitive information due to incorrect group handling in EMC Documentum TaskSpace.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6wgh-qx94-55f5

## What is CVE-2014-0629?

CVE-2014-0629 is a high-severity vulnerability in n/a, published on 6 Mar 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EMC Documentum TaskSpace (TSP) 6.7SP1 before P25 and 6.7SP2 before P11 does not properly handle the interaction between the dm_world group and the dm_superusers_dynamic group, which allows remote authenticated users to obtain sensitive information and gain privileges in opportunistic circumstances by leveraging an incorrect group-addition implementation.

Weakness: CWE-264

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

It affects 1 product.


Products: Emc Documentum Taskspace.

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

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

## Is CVE-2014-0629 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-0629 is a high-severity vulnerability in n/a, published on 6 Mar 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-0629 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-0629/ (Markdown: https://insights.sbomify.com/CVE-2014-0629/index.md)
```

## Sources

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

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