GHSA-446m-hmmm-hm8m
CRITICALCkan remote code execution and private information access via crafted resource ids
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
ckan🐍ckanReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Specific vulnerabilities:
- Arbitrary file write in
resource_createandpackage_updateactions, using theResourceUploaderobject. Also reachable viapackage_create,package_revise, andpackage_patchvia calls topackage_update. - Remote code execution via unsafe pickle loading, via Beaker's session store when configured to use the file session store backend.
- Potential DOS due to lack of a length check on the resource id.
- Information disclosure: A user with permission to create a resource can access any other resource on the system if they know the id, even if they don't have access to it.
- Resource overwrite: A user with permission to create a resource can overwrite any resource if they know the id, even if they don't have access to it.
Impact
A user with permissions to create or edit a dataset can upload a resource with a specially crafted id to write the uploaded file in an arbitrary location. This can be leveraged to Remote Code Execution via Beaker's insecure pickle loading.
Patches
All the above listed vulnerabilities have been fixed in CKAN 2.9.9 and CKAN 2.10.1 The patches for CKAN 2.9 should apply easily to previous CKAN versions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ckan | all versions | 2.9.9 |
| 🐍PyPI | ckan | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ckan to 2.9.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-446m-hmmm-hm8m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-446m-hmmm-hm8m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-446m-hmmm-hm8m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-446m-hmmm-hm8m in your dependencies?
O3 detects GHSA-446m-hmmm-hm8m across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.