CVE-2015-0912
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 · uneditedEasyCTF before 1.4 allows remote authenticated users to write executable content to files via unspecified vectors.
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 confidenceEasyCTF before version 1.4 contains a vulnerability allowing authenticated remote users to write executable content to files on the server. This appears to be a file upload/write validation issue where the application fails to properly restrict the type of content that authenticated users can save to the filesystem.
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.3CVSS 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
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Identify EasyCTF versionCheck the application's version file, footer, or admin panel for the installed EasyCTF version numberAffected if The installed version is 1.3 or lower (1.0, 1.1, 1.2, 1.3)
-
Verify user authentication is enabledCheck if the application has user registration and login functionality enabled and accessibleAffected if Unauthenticated users can register or authenticated users can access the system
-
Confirm file upload feature existsLook for file upload functionality in the challenge creation, submission, or user profile sections of the applicationAffected if The application allows authenticated users to upload or save files to the server
-
Check upload directory locationExamine the web server configuration and application settings to determine where uploaded files are stored relative to the web rootAffected if Uploaded files are stored within the web-accessible document root (htdocs, public_html, or equivalent)
-
Inspect file type validationReview the application's file upload code or settings to see what content types and extensions are acceptedAffected if The application does not properly validate file content or allows executable extensions (php, js, sh, etc.) to be uploaded
A user is affected if EasyCTF version 1.3 or lower is installed, the file upload feature is accessible to authenticated users, and uploaded files can be executed from the web root.
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 to EasyCTF version 1.4 or later. Additionally, implement strict file type validation, store uploaded files outside web-accessible directories, and disable script execution in upload directories.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0912 — 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-2015-0912 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