CVE-2023-32321

Specific vulnerabilities:

• Arbitrary file write in resource_create and package_update actions, using the ResourceUploader object. Also reachable via package_create, package_revise, and package_patch via calls to package_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.

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2023-32321 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.9); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2023-32321? CVE-2023-32321 is a critical-severity improper input validation vulnerability in ckan (pip), affecting versions < 2.9.9. It is fixed in 2.9.9. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2023-32321? CVE-2023-32321 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of ckan are affected by CVE-2023-32321? ckan (pip) versions < 2.9.9 is affected.
4. Is there a fix for CVE-2023-32321? Yes. CVE-2023-32321 is fixed in 2.9.9. Upgrade to this version or later.
5. Is CVE-2023-32321 exploitable, and should I be worried? Whether CVE-2023-32321 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-32321 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-32321? Upgrade ckan to 2.9.9 or later.