CVE-2018-10211
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 · uneditedAn issue was discovered in Vaultize Enterprise File Sharing 17.05.31. There is improper authorization when listing the history of another user via a modified "vaultize_session_id" value in a cookie.
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 confidenceVaultize Enterprise File Sharing 17.05.31 contains an Insecure Direct Object Reference (IDOR) vulnerability where manipulating the vaultize_session_id cookie value allows an authenticated user to view another user's history. The application fails to properly validate that the session ID corresponds to the user whose history is being requested.
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= 17.05.31CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 Vaultize Enterprise File Sharing versionLocate the installed version of Vaultize Enterprise File Sharing by checking the application UI (typically in About or Settings), or by querying the application's version endpoint if availableAffected if The installed version is exactly 17.05.31
-
Verify vaultize_session_id cookie presenceLog into the application and inspect browser cookies or HTTP traffic to confirm the vaultize_session_id cookie is used for session managementAffected if The vaultize_session_id cookie exists and is used to track user sessions
-
Check session validation on history endpointIntercept a request to the user history endpoint (typically /history or /user/history), modify the vaultize_session_id cookie value to another user's session ID, and observe if the application returns that user's data without authorizationAffected if The application returns another user's history data when using a different user's session ID without proper authorization validation
A user is affected if Vaultize Enterprise File Sharing version 17.05.31 is installed and the application allows viewing other users' history by modifying the vaultize_session_id cookie value.
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 dataImplement server-side authorization checks to verify the session owner matches the requested user history, and validate that the authenticated user has permission to access the requested data.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10211 — 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-2018-10211 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