Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-446m-hmmm-hm8m
No affected components available
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.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Active exploitation in the wild has been confirmed. Immediate patching or mitigation is required.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard