CVE-2022-38540
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 · uneditedArchery v1.4.0 to v1.8.5 was discovered to contain a SQL injection vulnerability via the ThreadIDs parameter in the create_kill_session interface.
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 confidenceSQL injection vulnerability in Archery v1.4.0 through v1.8.5 allows unauthenticated attackers to inject malicious SQL queries via the ThreadIDs parameter in the create_kill_session API endpoint, potentially leading to unauthorized database access, data exfiltration, or complete system compromise.
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>= 1.4.0, < 1.9.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if Archery is deployedCheck for running Archery DMS service via process list (ps aux | grep archery) or by reviewing installed packages (pip show archery or docker ps). Look for web service listening on typical ports like 8000 or 8080.Affected if Archery DMS is installed and running in the environment
-
Determine installed Archery versionRun 'archery --version' or check the version file in the installation directory. If running via Docker, check the image tag. For pip installations: pip show archery-sdk or check requirements/version files in the application directory.Affected if Installed version is >= 1.4.0 and < 1.9.0
-
Locate the create_kill_session endpointReview application routing files (urls.py) or API documentation for the /create_kill_session endpoint. This is typically found under the sqlquery or executor module.Affected if The create_kill_session API endpoint exists and is accessible in the application
-
Verify ThreadIDs parameter exposureExamine the create_kill_session view function in the source code. Check if the ThreadIDs parameter is directly used in a database query without parameterized binding. Look for string concatenation or f-string usage with SQL queries.Affected if ThreadIDs parameter is processed via raw SQL concatenation rather than parameterized queries
The environment is affected if running Archery versions 1.4.0 through 1.8.5 with the create_kill_session endpoint exposed and using unparameterized SQL queries for the ThreadIDs parameter.
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 · scoped1.9.0
Upgrade to v1.8.6 or later, or implement proper input validation and parameterized queries for the ThreadIDs parameter in the create_kill_session interface to remediate the SQL injection.
1.9.0 or later
- 1. Backup the current Archery installation and database before proceeding with any upgrade
- 2. Review the official Archery release notes and changelog for version 1.9.0 to understand changes and any migration requirements
- 3. Upgrade Archery to version 1.9.0 or later following the official installation/upgrade documentation for your deployment method
- 4. After upgrade, verify the application starts successfully and all services are running
- 5. Test the create_kill_session interface with the ThreadIDs parameter to confirm the SQL injection vulnerability has been remediated
- 6. Monitor application logs for any errors or unusual activity following the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38540 — 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-38540 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