CVE-2015-8747
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 · uneditedThe multifilesystem storage backend in Radicale before 1.1 allows remote attackers to read or write to arbitrary files via a crafted component name.
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 confidenceRadicale before version 1.1 contains a path traversal vulnerability in its multifilesystem storage backend. Attackers can craft malicious component names containing path traversal sequences (e.g., ../../) to read or write arbitrary files on the server, leading to complete system compromise.
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.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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/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 Radicale versionRun 'radicale --version' or check the package version via your system package manager (pip show radicale, dpkg -l radicale, etc.)Affected if The installed version is 1.0.1 or earlier
-
Verify multifilesystem storage is in useInspect the Radicale configuration file (typically ~/.config/radicale/config or /etc/radicale/config) and look for the [storage] section with 'type' set to 'radicale.storage.multi'Affected if The storage type is set to radicale.storage.multi with filesystem backend
-
Review collection names for traversal patternsExamine the collection directories under the file storage path (defined by 'filesystem' in [storage] section) and check for any collection names containing '../' sequencesAffected if Any collection directory or file name contains path traversal sequences like ../
-
Audit recently created files outside expected directoriesList all files in the Radicale storage root and parent directories to identify any unexpected files that may have been created via path traversalAffected if Files exist outside the designated storage directory
You are affected if Radicale version 1.0.1 or earlier is running with the multifilesystem storage backend enabled, and either suspicious collection names with ../ or unexpected files outside the storage directory are present.
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 Radicale to version 1.1 or later which contains the fix for proper path sanitization in the storage backend.
Radicale 1.1 or later
- 1. Back up your Radicale configuration and data directory before upgrading.
- 2. Stop the Radicale service.
- 3. Upgrade Radicale to version 1.1 or later using your system's package manager or pip (e.g., pip install --upgrade Radicale).
- 4. Verify the upgrade was successful by checking the installed version (radicale --version).
- 5. Restart the Radicale service.
- 6. Test that CalDAV/CardDAV functionality works correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2015-8747 — 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-8747 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