CVE-2022-43685
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCKAN through 2.9.6 account takeovers by unauthenticated users when an existing user id is sent via an HTTP POST request. This allows a user to take over an existing account including superuser accounts.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCKAN versions through 2.9.6 contain an Insecure Direct Object Reference (IDOR) vulnerability that allows unauthenticated account takeover. An attacker can take over any existing user account, including privileged superuser accounts, by submitting an HTTP POST request containing a known or guessed user ID.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.8.12>= 2.9.0, < 2.9.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed CKAN versionCheck the installed CKAN version by examining the source code version file, package metadata, or running: cat /usr/lib/ckan/default/src/ckan/CHANGELOG.rst | head -20 or pip show ckanAffected if Version is below 2.8.12, or >= 2.9.0 but below 2.9.7
-
Verify if user registration is enabledCheck the CKAN configuration file (usually development.ini or production.ini) for the parameter ckan.auth.create_user_view_via_web = true or examine the site settings via the web interface at /ckan-admin/configAffected if User registration is enabled and the CKAN version is in the affected range
-
Review user account modificationsQuery the user table in the CKAN database for recent password reset or security-related changes: SELECT id, name, email, created, last_login from user ORDER BY created DESC LIMIT 20;Affected if Unexpected user account changes exist that were not initiated by legitimate administrators
-
Check for unauthorized superuser accountsQuery the database for users with sysadmin privileges: SELECT id, name, email from user where sysadmin = true;Affected if New or unexpected sysadmin accounts appear that were not created by known administrators
You are affected if your CKAN version is below 2.8.12 or between 2.9.0 and 2.9.6 inclusive AND user registration is enabled, allowing unauthenticated attackers to hijack any user account.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.8.122.9.7
Upgrade CKAN to version 2.9.7 or later which contains the security fix. Until patched, disable user registration if not required and monitor for unauthorized account access.
CKAN 2.8.12 or later for 2.8.x line; CKAN 2.9.7 or later for 2.9.x line
- 1. Back up your CKAN database and configuration files before upgrading
- 2. For CKAN 2.8.x instances: upgrade to CKAN version 2.8.12 or later
- 3. For CKAN 2.9.x instances: upgrade to CKAN version 2.9.7 or later
- 4. After upgrading, verify that the instance starts successfully
- 5. Test that user account functionality works correctly after the upgrade
- 6. Confirm the vulnerability is fixed by verifying that unauthenticated users can no longer trigger account takeover via HTTP POST requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43685 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-43685 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data