# CVE-2017-2766: Auth bypass in EMC Documentum eRoom EMC Documentum eRoom version 7.4.4, EMC Documentum eRoom version 7.4.4 SP1, EMC Documentum eRoom version prior to 7.4.5 P04, EMC Documentum eRoom version prior to 7.5.0 P01

> Attackers can change passwords without verification, potentially compromising user accounts in EMC Documentum eRoom.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 3 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fgmj-4xc2-m385

## What is CVE-2017-2766?

CVE-2017-2766 is a critical authentication bypass vulnerability in EMC Documentum eRoom EMC Documentum eRoom version 7.4.4, EMC Documentum eRoom version 7.4.4 SP1, EMC Documentum eRoom version prior to 7.4.5 P04, EMC Documentum eRoom version prior to 7.5.0 P01, published on 3 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC Documentum eRoom version 7.4.4, EMC Documentum eRoom version 7.4.4 SP1, EMC Documentum eRoom version prior to 7.4.5 P04, EMC Documentum eRoom version prior to 7.5.0 P01 includes an unverified password change vulnerability that could potentially be exploited by malicious users to compromise the affected system.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2017-2766?

It affects 1 product.


Products: Emc Documentum Eroom.

## How do I fix CVE-2017-2766?

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

## Is CVE-2017-2766 being exploited?

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

## Other vulnerabilities in EMC Documentum eRoom EMC Documentum eRoom version 7.4.4, EMC Documentum eRoom version 7.4.4 SP1, EMC Documentum eRoom version prior to 7.4.5 P04, EMC Documentum eRoom version prior to 7.5.0 P01

- [CVE-2011-1741](https://insights.sbomify.com/CVE-2011-1741/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-2739](https://insights.sbomify.com/CVE-2011-2739/): File upload in n/a (high 8.5)
- [CVE-2012-0398](https://insights.sbomify.com/CVE-2012-0398/): Auth bypass in n/a (high 7.5)
- [CVE-2013-3286](https://insights.sbomify.com/CVE-2013-3286/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2012-0404](https://insights.sbomify.com/CVE-2012-0404/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2766 and fix it if it is affected.

What it is: CVE-2017-2766 is a critical authentication bypass vulnerability in EMC Documentum eRoom EMC Documentum eRoom version 7.4.4, EMC Documentum eRoom version 7.4.4 SP1, EMC Documentum eRoom version prior to 7.4.5 P04, EMC Documentum eRoom version prior to 7.5.0 P01, published on 3 Feb 2017. 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-2017-2766 in the wild and no public exploit code.

Affected product: EMC Documentum eRoom EMC Documentum eRoom version 7.4.4, EMC Documentum eRoom version 7.4.4 SP1, EMC Documentum eRoom version prior to 7.4.5 P04, EMC Documentum eRoom version prior to 7.5.0 P01. 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-2017-2766/ (Markdown: https://insights.sbomify.com/CVE-2017-2766/index.md)
```

## Sources

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

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