dbcve.org
Documentum EroomApplication · Emc

CVE-2011-1741

HIGH · 10.0 CVSS v2.0 Published 2011-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Stack-based buffer overflow in ftserver.exe in the OpenText Hummingbird Client Connector, as used in the Indexing Server in EMC Documentum eRoom 7.x before 7.4.3.f and other products, allows remote attackers to execute arbitrary code by sending a crafted message over TCP.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in ftserver.exe in OpenText Hummingbird Client Connector allows remote attackers to execute arbitrary code by sending crafted TCP messages to the Indexing Server component in EMC Documentum eRoom 7.x before 7.4.3.f and related products.

MitigationUpgrade EMC Documentum eRoom to version 7.4.3.f or later, or apply vendor-provided patches for the Hummingbird Client Connector; if patching is not immediately feasible, restrict network access to the Indexing Server port via firewall or network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Documentum EroomApplication
Affected:= 7.4.1= 7.4.2= 7.4.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify EMC Documentum eRoom installation and version
    Locate the eRoom installation directory (typically under the installation path for Documentum eRoom) and check the version information in the product manifest, registry, or about dialog. Common locations include the program's main directory or version file.
    Affected if The installed version is 7.4.1, 7.4.2, or 7.4.3
  2. Locate and verify the ftserver.exe binary
    Search for the file ftserver.exe in the eRoom installation directory, specifically within the Indexing Server component folder. Check the file properties to confirm it is the Hummingbird Client Connector Indexing Server component.
    Affected if ftserver.exe exists and is part of the installed eRoom version 7.4.1-7.4.3
  3. Confirm the Indexing Server service is running
    Check Windows services or process list for the Indexing Server service (often named related to Hummingbird or eRoom Indexing) that runs ftserver.exe. Use Task Manager or command line tools like tasklist or sc query to identify running processes.
    Affected if The Indexing Server process (ftserver.exe) is currently running
  4. Check network exposure of the Indexing Server port
    Review firewall rules, network configuration, or listening ports to determine if the Indexing Server TCP port is accessible from network hosts. Use netstat or similar tools to identify listening ports associated with ftserver.exe.
    Affected if The Indexing Server port is exposed to untrusted network segments

A system is affected if EMC Documentum eRoom versions 7.4.1, 7.4.2, or 7.4.3 are installed with the Indexing Server (ftserver.exe) running and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade EMC Documentum eRoom to version 7.4.3.f or later, or apply vendor-provided patches for the Hummingbird Client Connector; if patching is not immediately feasible, restrict network access to the Indexing Server port via firewall or network segmentation.

Recommended fix High confidence

Documentum eRoom 7.4.3.f or later

  1. Identify the current Documentum eRoom version running in the environment
  2. Backup the existing eRoom installation, configuration files, and database
  3. Download Documentum eRoom version 7.4.3.f or later from OpenText/EMC support portal
  4. Stop the eRoom indexing server and related services
  5. Install the upgraded version 7.4.3.f following the vendor upgrade documentation
  6. Restart the eRoom services and verify ftserver.exe is running correctly
  7. Validate that the stack-based buffer overflow vulnerability is remediated
Caveat Review upgrade documentation for any configuration changes or migration requirements between 7.4.x versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Documentum Eroom Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1741 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data