CVE-2016-1606
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 · uneditedMultiple stack-based buffer overflows in COM objects in Micro Focus Rumba 9.4.x before 9.4 HF 13960 allow remote attackers to execute arbitrary code via (1) the NetworkName property value to ObjectXSNAConfig.ObjectXSNAConfig in iconfig.dll, (2) the CPName property value to ObjectXSNAConfig.ObjectXSNAConfig in iconfig.dll, (3) the PrinterName property value to ProfileEditor.PrintPasteControl in ProfEdit.dll, (4) the Data argument to the WriteRecords function in FTXBIFFLib.AS400FtxBIFF in FtxBIFF.dll, (5) the Serialized property value to NMSECCOMPARAMSLib.SSL3 in NMSecComParams.dll, (6) the UserName property value to NMSECCOMPARAMSLib.FirewallProxy in NMSecComParams.dll, (7) the LUName property value to ProfileEditor.MFSNAControl in ProfEdit.dll, (8) the newVal argument to the Load function in FTPSFTPLib.SFtpSession in FTPSFtp.dll, or (9) a long Host field in the FTP Client.
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 confidenceMultiple stack-based buffer overflow vulnerabilities exist in COM objects within Micro Focus Rumba 9.4.x before 9.4 HF 13960 across nine different DLLs and COM interfaces (iconfig.dll, ProfEdit.dll, FtxBIFF.dll, NMSecComParams.dll, FTPSFtp.dll). Attackers can execute arbitrary code by passing oversized values to properties like NetworkName, CPName, PrinterName, Serialized, UserName, LUName, or arguments like Data and newVal, or via the FTP Client Host field.
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= 9.4CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Detect if Rumba is installedCheck for Rumba installation directory (typically in Program Files or Program Files (x86)), or look for rumba.exe process running, or check registry under HKLM\SOFTWARE\Micro Focus or HKLM\SOFTWARE\Wow6432Node\Micro Focus for Rumba entriesAffected if Rumba is not found on the system, so the CVE does not apply
-
Identify installed Rumba versionRight-click on rumba.exe in the installation directory, select Properties, and check the File Version field; alternatively, check the Windows registry under the Rumba installation key for a Version valueAffected if Version is 9.4.x and is earlier than 9.4 HF 13960, indicating the system may be vulnerable
-
Verify presence of affected DLLsCheck the Rumba installation directory for the presence of these DLLs: iconfig.dll, ProfEdit.dll, FtxBIFF.dll, NMSecComParams.dll, FTPSFtp.dllAffected if Any of these five DLLs exist in the Rumba directory, the COM objects they contain could be exploitable if the version is unpatched
-
Confirm COM objects are accessibleOpen Component Services (comexp.msc) or use regedit to check registry under HKCR\CLSID for CLSIDs associated with these DLLs, or attempt to instantiate the COM objects via a script (e.g., CreateObject in VBScript)Affected if The COM objects can be instantiated and the installed version is unpatched, the buffer overflow conditions exist
A system is affected if Micro Focus Rumba 9.4 is installed with a version earlier than 9.4 HF 13960 and any of the five affected DLLs (iconfig.dll, ProfEdit.dll, FtxBIFF.dll, NMSecComParams.dll, FTPSFtp.dll) are present with accessible COM interfaces.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Micro Focus Rumba version 9.4 HF 13960 or later to address all nine buffer overflow vulnerabilities in the affected COM objects; until patched, restrict network access to Rumba services and disable unnecessary COM object interfaces.
Rumba 9.4 HF 13960 or later
- Identify the current installed version of Micro Focus Rumba
- Download hotfix HF 13960 or later from Micro Focus official support portal
- Apply the hotfix according to Micro Focus installation instructions
- Restart any Rumba services if required
- Verify the version now shows 9.4 HF 13960 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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