CVE-2013-0130
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 · uneditedMultiple buffer overflows in Core FTP before 2.2 build 1769 allow remote FTP servers to execute arbitrary code or cause a denial of service (application crash) via a long directory name in a (1) DELE, (2) LIST, or (3) VIEW command.
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 confidenceBuffer overflow vulnerability in Core FTP client versions before 2.2 build 1769. When the client connects to a malicious FTP server, long directory names in server responses to DELE, LIST, or VIEW commands overflow a buffer, allowing potential arbitrary code execution on the client or causing application crash (DoS).
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<= 2.2CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/A:P
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 Core FTP client installationCheck Program Files for Core FTP folder, or search for coreftp.exe in common installation directories. The executable is typically named coreftp.exeAffected if Core FTP client is installed on the system
-
Determine installed Core FTP versionRight-click coreftp.exe, select Properties, then view the Details tab for version information. Alternatively, launch Core FTP and look for version info in the About or Help menuAffected if Version displayed is earlier than 2.2 build 1769, or shows only '2.2' without a build number greater than 1769
-
Confirm the build numberIf version shows only '2.2' with no build number, this is considered affected since the fix requires build 1769 specificallyAffected if Build number is absent or is 1768 or lower
-
Understand attack prerequisiteRecognize this is a client-side vulnerability triggered when the Core FTP client connects to a malicious FTP server. The vulnerability affects responses to DELE, LIST, or VIEW commandsAffected if The client connects to untrusted or unknown FTP servers using vulnerable Core FTP version
A user is affected if their Core FTP client version is 2.2 with build lower than 1769, or any version below 2.2, and they connect to untrusted FTP servers.
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 dataUpgrade Core FTP client to version 2.2 build 1769 or later. Users should avoid connecting to untrusted or unknown FTP servers until the update is applied, as this is a client-side vulnerability triggered by malicious server responses.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0130 — 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-2013-0130 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