CVE-2012-2999
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 cross-site request forgery (CSRF) vulnerabilities in the web interface in Cerberus FTP Server before 5.0.5.0 allow remote attackers to hijack the authentication of administrators for requests that (1) add a user account or (2) reconfigure the state of the FTP service, as demonstrated by a request to usermanager/users/modify.
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 confidenceMultiple cross-site request forgery (CSRF) vulnerabilities exist in the web interface of Cerberus FTP Server versions prior to 5.0.5.0. The vulnerabilities allow remote attackers to hijack administrator authentication and perform unauthorized actions including adding user accounts and reconfiguring the FTP service state through malicious requests to endpoints like usermanager/users/modify.
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<= 5.0.4.3= 1.0= 1.01= 1.1= 1.2= 1.02= 1.03= 1.5= 1.05= 1.6= 1.7= 1.22CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Confirm Cerberus FTP Server is installedLocate Cerberus FTP Server on the system - check for the service named 'Cerberus FTP Server' in Windows Services or look for the installation directory (commonly C:\Program Files\Cerberus FTP Server or C:\Program Files (x86)\Cerberus FTP Server)Affected if Cerberus FTP Server software is present on the system
-
Identify the installed versionOpen the Cerberus FTP Server GUI, go to Help > About, or check the version displayed in the server console window. Alternatively, locate a version file in the installation directoryAffected if The installed version is any release prior to 5.0.5.0, including versions 5.0.4.3, 1.0, 1.01, 1.1, 1.2, 1.02, 1.03, 1.5, 1.05, 1.6, 1.7, or 1.22
-
Verify the web interface is enabledIn Cerberus FTP Server, go to Server > Server Options > Interfaces and confirm the HTTP/HTTPS web interface listener is configured and enabledAffected if The HTTP or HTTPS web interface is actively listening and accessible
-
Review user accounts for unauthorized modificationsIn the Cerberus GUI, navigate to Users > User Manager and inspect the list of user accounts. Check for any unexpected admin or standard user accounts that were not intentionally createdAffected if Unknown or unauthorized user accounts exist in the user list
The environment is affected if Cerberus FTP Server version is below 5.0.5.0 and the web interface is enabled, allowing CSRF attacks to modify users or service configuration.
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 Cerberus FTP Server to version 5.0.5.0 or later, which contains the CSRF protection fixes. As an interim measure, enforce strict network access controls to limit web interface exposure and monitor for suspicious administrative actions.
- Consultation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2999 — 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-2012-2999 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