CVE-2010-20107: FTP Synchronizer Professional <= 4.0.73.274 Stack Buffer Overflow
A stack-based buffer overflow exists in FTP Synchronizer Professional <= v4.0.73.274. When the client connects to an FTP server and issues a LIST command—typically during sync preview or profile creation—the server’s response containing an overly long filename triggers a buffer overflow. This results in the corruption of the Structured Exception Handler (SEH), potentially allowing remote code execution.
Security readout for executives and security teams
Plain-English summary
This vulnerability affects old FTP Synchronizer Professional clients. If a user connects the client to a malicious or compromised FTP server, a crafted directory listing can crash the client and may run attacker-controlled code on that user’s Windows system.
Executive priority
Prioritize if the organization still uses this legacy FTP client or connects workstations to partner FTP servers. The risk is high because compromise could execute code in the user context, but exposure may be narrow and should be validated first.
Technical view
FTP Synchronizer Professional <= 4.0.73.274 has a stack-based buffer overflow in handling FTP LIST responses containing an overly long filename. The supplied description says this corrupts SEH and may allow remote code execution. CVSS 4.0 score is 8.5 high, with user interaction required.
Likely exposure
Exposure is likely limited to organizations still running FTP Synchronizer Professional <= 4.0.73.274, especially on workstations that connect to external, legacy, or partner FTP servers. Evidence for affected CPEs and default status is incomplete in the bundle.
Exploitation context
The bundle includes public exploit references, including Exploit-DB and Metasploit, but KEV is false and no cited source establishes active exploitation. Treat this as a credible client-side exploitation risk, not confirmed in-the-wild activity.
Researcher notes
The trigger is a malformed FTP LIST response with an overly long filename during client operations such as sync preview or profile creation. The bundle supports SEH corruption and potential RCE, but does not provide a vendor patch statement or evidence of active exploitation.
Mitigation direction
Inventory endpoints for FTP Synchronizer Professional and confirm installed versions.
Remove the client where business use is no longer required.
Check Liuxz Software or product guidance for supported fixed versions.
Upgrade or replace vulnerable installs if vendor guidance confirms a fixed release.
Limit use to trusted FTP servers until remediation is complete.
Avoid syncing from untrusted, anonymous, or externally controlled FTP servers.
Validation and detection
Confirm whether FTP Synchronizer Professional is installed on managed endpoints.
Record exact installed version and compare with <= 4.0.73.274.
Review user workflows for connections to external FTP servers.
Check EDR or crash telemetry for FTP Synchronizer client faults.
Verify remediation by confirming removal, replacement, or vendor-supported upgrade.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.