# CVE-2024-27097: Potential log injection in reset user endpoint in ckan

> Attackers can inject false entries or corrupt log files via unfiltered user input in the reset endpoint, requiring an upgrade to CKAN.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Mar 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-8g38-3m6v-232j, PYSEC-2026-1251

## What is CVE-2024-27097?

CVE-2024-27097 is a medium-severity vulnerability in ckan, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A user endpoint didn't perform filtering on an incoming parameter, which was added directly to the application log. This could lead to an attacker injecting false log entries or corrupt the log file format. This has been fixed in the CKAN versions 2.9.11 and 2.10.4. Users are advised to upgrade. Users unable to upgrade should override the `/user/reset` endpoint to filter the `id` parameter in order to exclude newlines.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-27097?

5 open source packages ship an affected version, including ckan. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ckan` | PyPI | All versions | 2.9.11, 2.10.4 |
| `ckan` | PyPI | All versions | 2.9.11 |
| `ckan` | PyPI | All versions | 2.9.11 |
| `ckan` | PyPI | From 2.10.0 | 2.10.4 |
| `ckan` | PyPI | From 2.10.0 | 2.10.4 |

Products: Okfn Ckan.

## How do I fix CVE-2024-27097?

Upgrade ckan to a fixed version for your release line: 2.9.11 or 2.10.4.

## Is CVE-2024-27097 being exploited?

There is no known exploitation of CVE-2024-27097 in the wild and no public exploit code.

## Other vulnerabilities in ckan

- [CVE-2023-32321](https://insights.sbomify.com/CVE-2023-32321/): CKAN remote code execution and private information access via crafted resource ids (critical 9.8)
- [CVE-2023-32696](https://insights.sbomify.com/CVE-2023-32696/): Excessive permissions for ckan user (high 8.8)
- [CVE-2022-43685](https://insights.sbomify.com/CVE-2022-43685/): CKAN contains Improper Authentication leading to account takeover (high 8.8)
- [CVE-2023-22746](https://insights.sbomify.com/CVE-2023-22746/): CKAN is vulnerable to session secret shared across instances using Docker images (high 8.6)
- [CVE-2026-42031](https://insights.sbomify.com/CVE-2026-42031/): CKAN: Unauthenticated SQL Injection and Authorization Bypass in `datastore_search_sql` (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27097 and fix it if it is affected.

What it is: CVE-2024-27097 is a medium-severity vulnerability in ckan, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-27097 in the wild and no public exploit code.

Affected packages and fixed versions:
- ckan (PyPI): affected all versions; fixed in 2.9.11, 2.10.4
- ckan (PyPI): affected all versions; fixed in 2.9.11
- ckan (PyPI): affected all versions; fixed in 2.9.11
- ckan (PyPI): affected from 2.10.0; fixed in 2.10.4
- ckan (PyPI): affected from 2.10.0; fixed in 2.10.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-27097/ (Markdown: https://insights.sbomify.com/CVE-2024-27097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27097
- OSV: https://osv.dev/vulnerability/CVE-2024-27097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-27097/
Summaries are generated and may contain mistakes; the official description above is the record.