{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-22746 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-22746 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22746 is a high-severity vulnerability in ckan, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22746 and fix it if it is affected.\n\nWhat it is: CVE-2023-22746 is a high-severity vulnerability in ckan, published on 3 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-22746 in the wild and no public exploit code.\n\nAffected product: ckan. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-22746/ (Markdown: https://insights.sbomify.com/CVE-2023-22746/index.md)","id":"CVE-2023-22746","markdown":"https://insights.sbomify.com/CVE-2023-22746/index.md","name":"CVE-2023-22746","record":{"aliases":["GHSA-pr8j-v4c8-h62x"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"configuration_change","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"CKAN Docker images","requires_auth":"none","summary":"Attackers can forge authentication requests in CKAN Docker instances using default shared secrets, leading to account takeover.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ckan","vendor":"okfn"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-344","name":"Use of Invariant Value in Dynamically Changing Context"},{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"CKAN is an open-source DMS (data management system) for powering data hubs and data portals. When creating a new container based on one of the Docker images listed below, the same secret key was being used by default. If the users didn't set a custom value via environment variables in the `.env` file, that key was shared across different CKAN instances, making it easy to forge authentication requests. Users overriding the default secret key in their own `.env` file are not affected by this issue. Note that the legacy images (ckan/ckan) located in the main CKAN repo are not affected by this issue. The affected images are ckan/ckan-docker, (ckan/ckan-base images), okfn/docker-ckan (openknowledge/ckan-base and openknowledge/ckan-dev images)\nkeitaroinc/docker-ckan (keitaro/ckan images).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"CKAN is vulnerable to session secret shared across instances using Docker images","id":"CVE-2023-22746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Multiple Unauthenticated Command Injections in the PAPI Protocol","id":"CVE-2023-22747"},"packages":[],"prev":{"headline":"Buffer Overlow in TSS2_RC_Decode in tpm2-tss","id":"CVE-2023-22745"},"products":["ckan"],"published":"2023-02-03","related":[{"cvss_score":9.8,"headline":"CKAN remote code execution and private information access via crafted resource ids","id":"CVE-2023-32321","kev_date_added":null,"published":"2023-05-26"},{"cvss_score":8.8,"headline":"Excessive permissions for ckan user","id":"CVE-2023-32696","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":8.8,"headline":"CKAN contains Improper Authentication leading to account takeover","id":"CVE-2022-43685","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":8.3,"headline":"CKAN: Unauthenticated SQL Injection and Authorization Bypass in `datastore_search_sql`","id":"CVE-2026-42031","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":6.8,"headline":"CKAN has a Cross-site Scripting vector in the Datatables view plugin","id":"CVE-2024-41675","kev_date_added":null,"published":"2024-08-21"},{"cvss_score":6.7,"headline":"CKAN: Unauthenticated Authorization Bypass in `datastore_search_sql`","id":"CVE-2026-42032","kev_date_added":null,"published":"2026-05-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["ckan"]},"summary":"Attackers can forge authentication requests in CKAN Docker instances using default shared secrets, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2023-22746/"}