# 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.

- **Severity:** High 7.5 (`CVSS:3.0/UI:N/A:H/I:N/PR:N/AV:N/C:N/AC:L/S:U/RC:C/RL:O/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wf3w-6f2x-x7mg

## 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 (Out-of-bounds Read)

## Which versions are affected by CVE-2020-4767?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2023-32331/): IBM Connect:Express for UNIX denial of service (high 7.5)
- [CVE-2025-36137](https://insights.sbomify.com/CVE-2025-36137/): IBM Sterling Connect:Direct for UNIX command execution (high 7.2)
- [CVE-2018-1903](https://insights.sbomify.com/CVE-2018-1903/): Privilege escalation in Sterling Connect:Direct for UNIX (medium 6.7)
- [CVE-2023-29260](https://insights.sbomify.com/CVE-2023-29260/): IBM Sterling Connect:Express for UNIX server-side request forgery (medium 6.5)
- [CVE-2025-36063](https://insights.sbomify.com/CVE-2025-36063/): Multiple vulnerabilities were addressed in IBM Sterling Connect:Express for UNIX. (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-4767 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2020-4767 in the wild and no public exploit code.

Affected product: IBM Sterling Connect Direct for Microsoft Windows. 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-2020-4767/ (Markdown: https://insights.sbomify.com/CVE-2020-4767/index.md)
```

## Sources

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

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