CVE-2016-1505
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 filesystem storage backend in Radicale before 1.1 on Windows allows remote attackers to read or write to arbitrary files via a crafted path, as demonstrated by /c:/file/ignore.
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 on Windows contains a path traversal vulnerability in its filesystem storage backend. Attackers can craft malicious paths like /c:/file/ignore to access or modify files outside the intended storage directory, potentially leading to remote code execution or data exfiltration.
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 installation and versionRun 'radicale --version' or check the version reported by the server. If using a package manager, query the installed package version.Affected if The installed version is 1.0.1 or any version prior to 1.1
-
Confirm operating systemCheck if the system running Radicale is Windows (the path traversal flaw is specific to Windows environments).Affected if The operating system is Windows and Radicale version is <= 1.0.1
-
Identify storage backend in useExamine the Radicale configuration file (typically config.py or ~/.radicale/config) and look for the 'storage' or 'filesystem' backend setting.Affected if The filesystem storage backend is enabled (this is the component with the path traversal vulnerability)
-
Locate storage directoryIn the Radicale configuration, find the 'filesystem_folder' or 'stock' parameter that specifies where CalDAV/CardDAV data is stored.Affected if A storage directory is configured (the vulnerability allows escaping this directory to access arbitrary files on the Windows system)
A user is affected if they are running Radicale version 1.0.1 or earlier on Windows with the filesystem storage backend enabled.
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 Radicale version 1.1 or later. If immediate upgrade is not possible, implement strict input validation on path parameters and restrict the storage backend to a sandboxed directory.
Radicale >= 1.1
- 1. Check the current installed version of Radicale: `pip show radicale` or `radicale --version`
- 2. Back up your current configuration and data directory before upgrading
- 3. Upgrade Radicale using pip: `pip install --upgrade Radicale`
- 4. Verify the new version is installed: `pip show radicale` or `radicale --version`
- 5. Ensure the installed version is 1.1 or later
- 6. Restart the Radicale service
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2016-1505 — 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-2016-1505 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