Potential log injection in reset user endpoint in CKAN
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. ### Patches This has been fixed in the CKAN 2.9.11 and 2.10.4 versions ### Workarounds Override the `/user/reset` endpoint to filter the `id` parameter in order to exclude newlines
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-27097US | medium5.3 | — | ||
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 co… | ||||
02
references
External citations — patches, advisories, analysis.
- https://docs.ckan.org/en/2.10/changelog.html#v-2-10-4-2024-03-13WEB
- https://github.com/advisories/GHSA-8g38-3m6v-232jADVISORY
- https://github.com/ckan/ckanPACKAGE
- https://github.com/ckan/ckan/commit/5fa133e7e9019573066455b5d442e93c62b3fc93WEB
- https://github.com/ckan/ckan/commit/81b56c55e5e3651d7fcf9642cd5a489a9b62212cWEB
- https://github.com/ckan/ckan/commit/d81f411bff2da7347c343a83e17f5814475b5b64WEB
- https://github.com/ckan/ckan/security/advisories/GHSA-8g38-3m6v-232jWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-27097ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan