CVE-2017-1000002
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 · uneditedATutor versions 2.2.1 and earlier are vulnerable to a directory traversal and file extension check bypass in the Course component resulting in code execution. ATutor versions 2.2.1 and earlier are vulnerable to a directory traversal vulnerability in the Course Icon component resulting in information disclosure.
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 confidenceATutor versions 2.2.1 and earlier contain a directory traversal vulnerability combined with a file extension check bypass in the Course component, allowing authenticated attackers to upload arbitrary files and achieve remote code execution. A separate directory traversal vulnerability in the Course Icon component permits unauthorized access to sensitive files on the server, leading to information disclosure.
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.2.1CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify ATutor installation and versionLocate the ATutor installation directory on the web server and check the version file (typically version.php in the root or includes directory), or access the application's admin/about page to retrieve the version numberAffected if The installed version is 2.2.1 or lower
-
Verify Course upload functionality is presentNavigate to the Course management section of the ATutor web interface and locate any file upload feature for course content or assignmentsAffected if The Course upload feature exists and is accessible to authenticated users
-
Confirm Course Icon functionality existsAccess the Course Icon settings area within the course management section of the web interface, typically found under course settings or content modulesAffected if The Course Icon feature is present and accessible without additional authentication beyond basic site access
Your environment is affected if ATutor version 2.2.1 or lower is running and either the Course upload or Course Icon component is accessible.
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 to a version newer than 2.2.1 or apply vendor-supplied patches. If immediate patching is not possible, restrict write access to upload directories and disable script execution in upload paths via web server configuration.
ATutor 2.2.2 or later
- 1. Back up the entire ATutor installation directory and database before any upgrade
- 2. Download ATutor 2.2.2 (or the latest stable release) from the official ATutor website at www.atutor.ca
- 3. Follow the standard ATutor upgrade documentation to replace the existing files
- 4. Ensure the web server has appropriate file permissions after upgrade
- 5. Verify the Course and Course Icon components function correctly and that the path traversal vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000002 — 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-2017-1000002 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