CVE-2020-4767 Memory corruption in Sterling Connect Direct for Microsoft Windows
A remote attacker can cause a denial of service by sending a specially crafted request that triggers a buffer over-read, crashing the application.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2020-4767?
CVE-2020-4767 is a high-severity memory corruption vulnerability in IBM Sterling Connect Direct for Microsoft Windows, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
IBM 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.
Weakness: CWE-125
Which versions are affected by CVE-2020-4767?
It affects 1 product.
Products include Ibm Sterling Connect\.
How do I fix CVE-2020-4767?
No fix has been published for CVE-2020-4767 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2020-4767 being exploited?
There is no known exploitation of CVE-2020-4767 in the wild and no public exploit code.
Other vulnerabilities in IBM Sterling Connect Direct for Microsoft Windows
- CVE-2023-32331 IBM Connect:Express for UNIX denial of service
- CVE-2025-36137 IBM Sterling Connect:Direct for UNIX command execution
- CVE-2018-1903 Privilege escalation in Sterling Connect:Direct for UNIX
- CVE-2023-29260 IBM Sterling Connect:Express for UNIX server-side request forgery
- CVE-2025-36063 Multiple vulnerabilities were addressed in IBM Sterling Connect:Express for UNIX.
Sources
Also known as GHSA-wf3w-6f2x-x7mg.