CVE-2017-9517
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 · uneditedatmail before 7.8.0.2 has CSRF, allowing an attacker to upload and import users via CSV.
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 confidenceatmail before version 7.8.0.2 contains a Cross-Site Request Forgery (CSRF) vulnerability in its user management functionality. An attacker can craft a malicious webpage that, when visited by an authenticated administrator, silently triggers the CSV user upload and import feature without the administrator's knowledge or consent.
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<= 7.8.0.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 atmail versionAccess the atmail admin interface and navigate to the system information or about section. Alternatively, check the application source files for a version marker (often in a config file, changelog, or version.php).Affected if The installed version is 7.8.0.1 or earlier (any version <= 7.8.0.1).
-
Inspect CSV import feature for CSRF tokensLog in as administrator, access the user management section, and examine the HTTP requests when using the CSV upload/import feature. Check if the form or request includes a unique CSRF token parameter that is validated server-side.Affected if The CSV import functionality lacks CSRF token validation or uses predictable/static tokens.
-
Verify anti-CSRF implementation in user managementReview the application's source code for the user management module (specifically the CSV import handler). Look for anti-CSRF token generation and validation logic, such as session-bound tokens or SameSite cookie attributes.Affected if No anti-CSRF token validation is found in the user import/upload code.
You are affected if your atmail installation is version 7.8.0.1 or earlier AND the CSV user import feature lacks server-side CSRF token validation.
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 atmail to version 7.8.0.2 or later which includes CSRF protection tokens. Additionally, implement SameSite cookie attributes and ensure anti-CSRF tokens are required for all state-changing operations.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9517 — 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-9517 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