CVE-2014-1215
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 Server before 1.2 build 508 allow local users to gain privileges via vectors related to reading data from config.dat and Windows Registry.
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 confidenceCore FTP Server versions prior to 1.2 build 508 contain multiple buffer overflow vulnerabilities when parsing data from the config.dat file and Windows Registry. Local attackers can exploit these overflows to execute arbitrary code with elevated privileges, potentially achieving administrative access to the 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<= 1.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm Core FTP Server installationCheck for Core FTP Server service running on the system or look for the executable (coreftpserver.exe) in Program Files. Use 'services.msc' to list services or check for the program in Add/Remove Programs.Affected if Core FTP Server is found installed on the system
-
Identify installed version and build numberLocate the Core FTP Server executable or check the Windows Registry under HKLM\SOFTWARE\Core FTP Server for the Version or Build value. Right-click the executable, select Properties, and check the Details tab for version information.Affected if Version shows 1.2 with a build number lower than 508, or the exact version cannot be determined (assume vulnerable)
-
Locate config.dat fileSearch for the config.dat file in the Core FTP Server installation directory, typically found in the program folder where Core FTP Server is installed.Affected if config.dat file exists and is being used by Core FTP Server (the vulnerability triggers during parsing of this file)
-
Verify service runs with elevated privilegesCheck the service properties in services.msc to confirm if Core FTP Server runs under the Local System account or another account with elevated privileges.Affected if Service runs with elevated privileges (Local System or Administrator), which enables the arbitrary code execution vector described in the CVE
System is affected if Core FTP Server version 1.2 with build number below 508 is installed and the service runs with elevated privileges, allowing the config.dat or registry parsing buffer overflow to be exploited for privilege escalation.
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 Server to version 1.2 build 508 or later to obtain the vendor patch. Until then, restrict local access to trusted users and monitor for suspicious registry or config file modifications.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1215 — 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-2014-1215 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