CVE-2010-3099
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 · uneditedDirectory traversal vulnerability in SmartSoft Ltd SmartFTP Client 4.0.1124.0, and possibly other versions before 4.0 Build 1133, allows remote FTP servers to overwrite arbitrary files via a "..\" (dot dot backslash) in a filename. NOTE: some of these details are obtained from third party information.
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 · moderate confidenceThe SmartFTP Client versions prior to 4.0 Build 1133 contain a directory traversal vulnerability where a malicious FTP server can craft filenames containing '..\' sequences to cause the client to write files outside the intended target directory, allowing arbitrary file overwrite on the client system.
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<= 4.0.1124.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Verify SmartFTP Client is installedCheck for SmartFTP installation by looking in Program Files for the SmartFTP folder, or by running 'smartftp.exe' from common installation paths (C:\Program Files\SmartFTP Client\ or C:\Program Files (x86)\SmartFTP Client\). You can also check Add/Remove Programs for SmartFTP.Affected if SmartFTP Client is present on the system
-
Determine the installed SmartFTP versionLaunch SmartFTP Client and go to Help > About, or right-click the SmartFTP icon and select About. Note the version number and build number displayed.Affected if The version is 4.0 Build 1124 or earlier (versions prior to 4.0 Build 1133)
-
Confirm FTP transfer functionality is usedReview the client's transfer history or settings to confirm it is used to connect to remote FTP servers and download files. This vulnerability is triggered when downloading files from a malicious FTP server.Affected if The client is used to download files from remote FTP servers
You are affected if SmartFTP Client version 4.0 Build 1124 or earlier is installed and is used to download files from FTP servers, as the directory traversal flaw allows a malicious server to write files outside the intended download directory.
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.
dbcve · scopedUpgrade SmartFTP Client to version 4.0 Build 1133 or later to obtain the patch for this directory traversal vulnerability.
SmartFTP Client 4.0 Build 1133 or later
- 1. Visit the official SmartFTP website at www.smartftp.com to download the latest version
- 2. Download SmartFTP Client version 4.0 Build 1133 or later
- 3. Uninstall the current vulnerable version of SmartFTP from your system
- 4. Install the updated SmartFTP Client version 4.0 Build 1133 or newer
- 5. Verify the installed version by checking Help > About to confirm you are running a version beyond 4.0.1124.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3099 — 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-2010-3099 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