CVE-2020-5779
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 · uneditedA 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.
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 confidenceA buffer handling flaw in Trading Technologies Messaging daemon (ttmd.exe) allows an unauthenticated remote attacker to cause a denial of service by sending a specially crafted type 4 message with an overly long string parameter to TCP port 10200. The strcpy_s() function fails with an invalid parameter, causing the service to terminate unexpectedly.
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= 7.1.28.3CVSS 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.
-
Locate the Trading Technologies Messaging daemonCheck if ttmd.exe exists on the system by searching in typical installation paths such as C:\Program Files\Trading Technologies\ or C:\Program Files (x86)\Trading Technologies\, or use Task Manager to look for ttmd.exe running as a process.Affected if ttmd.exe is present and running on the system.
-
Identify the installed version of ttmd.exeRight-click on ttmd.exe in the installation folder, select Properties, then go to the Details tab to view the File Version. Alternatively, right-click the process in Task Manager and select Properties to view version information.Affected if The version is exactly 7.1.28.3.
-
Verify TCP port 10200 is listeningOpen Command Prompt and run: netstat -an | findstr :10200 or use PowerShell: Get-NetTCPConnection -LocalPort 10200 -State Listen to check if the service is bound and listening on port 10200.Affected if Port 10200 shows as LISTENING, indicating the vulnerable service is active and accepting connections.
-
Determine if the service is network accessibleFrom a remote system, attempt to telnet or connect to the target port: telnet <target_ip> 10200. From the local system, verify the firewall allows inbound connections on port 10200 using: netsh advfirewall firewall show rule name=all | findstr 10200Affected if Port 10200 is exposed to untrusted network segments, making the vulnerability reachable by remote attackers.
The environment is affected if ttmd.exe version 7.1.28.3 is running and TCP port 10200 is accessible from a network where untrusted actors could send specially crafted type 4 messages.
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 dataRestrict network access to TCP port 10200 using firewall rules or network segmentation to limit exposure to untrusted actors, and apply any vendor-supplied patches when available.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5779 — 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-5779 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