# CVE-2020-5779: Denial of service in Trading Technologies Messaging

> A flaw in Trading Technologies Messaging allows remote attackers to cause a denial of service by sending a malformed message to the default TCP port.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wwww-2qvw-46wq

## What is CVE-2020-5779?

CVE-2020-5779 is a high-severity denial of service vulnerability in Trading Technologies Messaging, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw in Trading Technologies Messaging 7.1.28.3 (ttmd.exe) relates to invalid parameter handling when calling strcpy_s() with an invalid parameter (i.e., a long src string parameter) as a part of processing a type 4 message sent to default TCP RequestPort 10200. It's been observed that ttmd.exe terminates as a result.

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

It affects 1 product.


Products: Tradingtechnologies Trading Technologies Messaging.

## How do I fix CVE-2020-5779?

No fix has been published for CVE-2020-5779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-5779 being exploited?

There is no known exploitation of CVE-2020-5779 in the wild and no public exploit code.

## Other vulnerabilities in Trading Technologies Messaging

- [CVE-2020-5778](https://insights.sbomify.com/CVE-2020-5778/): Denial of service in Trading Technologies Messaging (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5779 is a high-severity denial of service vulnerability in Trading Technologies Messaging, published on 2 Sep 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-5779 in the wild and no public exploit code.

Affected product: Trading Technologies Messaging. 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-5779/ (Markdown: https://insights.sbomify.com/CVE-2020-5779/index.md)
```

## Sources

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

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