CVE-2020-4767
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 · uneditedIBM Sterling Connect Direct for Microsoft Windows 4.7, 4.8, 6.0, and 6.1 could allow a remote attacker to cause a denial of service, caused by a buffer over-read. Bysending a specially crafted request, the attacker could cause the application to crash. IBM X-Force ID: 188906.
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 · moderate confidenceIBM Sterling Connect Direct for Microsoft Windows versions 4.7, 4.8, 6.0, and 6.1 contains a buffer over-read vulnerability that can be triggered remotely via specially crafted requests, causing the application to crash and resulting in denial of service.
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>= 4.7.0.0, < 4.7.0.7>= 4.8.0.0, < 4.8.0.3>= 6.0.0.0, < 6.0.0.4>= 6.1.0.0, < 6.1.0.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check if IBM Sterling Connect Direct is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' to list installed softwareAffected if IBM Sterling Connect Direct for Microsoft Windows is not present in the installed programs list
-
Locate the executable and confirm versionNavigate to the installation directory (commonly C:\Program Files\IBM\Connect-Direct or C:\Connect-Direct) and locate the main executable such as cdunix.exe or cdwin.exe. Right-click the executable and select Properties > Details to view the File VersionAffected if The File Version falls within any of these ranges: 4.7.0.0 through 4.7.0.6, 4.8.0.0 through 4.8.0.2, 6.0.0.0 through 6.0.0.3, or 6.1.0.0
-
Query the Windows Registry for versionRun 'reg query HKLM\SOFTWARE\IBM\Connect-Direct\CurrentVersion' or check the registry path where the application stores its version informationAffected if The queried version value matches any of the affected version ranges listed above
-
Verify if the service is running and listening on network portsOpen Services.msc to confirm the Connect Direct service is running, then run 'netstat -an | findstr LISTENING' to check if the application is listening on TCP ports (default ports are 1363, 1364, or custom configured ports)Affected if The service is running and bound to a network interface accessible remotely, increasing exposure to the vulnerability
-
Confirm patch level by checking for interim fixesConsult the IBM documentation or support portal for the specific patch identifiers related to CVE-2020-4767, then verify the installed fix level using the application's built-in version or maintenance commandsAffected if The installed fix level is earlier than 4.7.0.7, 4.8.0.3, 6.0.0.4, or 6.1.0.1, indicating the security patch has not been applied
A system is affected if IBM Sterling Connect Direct for Microsoft Windows is installed and the installed version falls within any of these vulnerable ranges: 4.7.0.0-4.7.0.6, 4.8.0.0-4.8.0.2, 6.0.0.0-6.0.0.3, or 6.1.0.0, and the service is exposed to network requests.
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.
From vendor data4.7.0.74.8.0.36.0.0.4
Apply IBM security patches for this vulnerability. Until patched, consider network segmentation and restricting access to affected systems to reduce attack surface.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4767 — 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-2020-4767 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