CVE-2022-38542
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 kill_session interface. The project has released an update, please upgrade to v1.9.0 and above.
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's kill_session interface allows attackers to inject malicious SQL queries through the ThreadIDs parameter. This critical flaw (CVSS 9.8) affects versions v1.4.0 through v1.8.5, potentially enabling unauthorized database access or data exfiltration.
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.
-
Check if Archery is installedLocate the Archery application directory or check for the 'archery' package using package managers or container image inspectionAffected if Archery software is present in the environment
-
Identify installed Archery versionCheck the version file, setup.py, requirements.txt, or use 'archery --version' if available. Common paths include /opt/archery/, /usr/local/archery/, or check the Docker image tagsAffected if Version is >= 1.4.0 and < 1.9.0
-
Verify kill_session endpoint existsInspect the web application's URL routing configuration (urls.py) or search for 'kill_session' route definitions in the source codeAffected if The kill_session route is defined and accessible via HTTP/HTTPS
-
Confirm ThreadIDs parameter handlingReview the kill_session view function code to confirm it accepts and processes the 'ThreadIDs' GET or POST parameter without proper parameterizationAffected if The ThreadIDs parameter is processed directly in SQL queries without sanitization
The environment is affected if Archery version is between v1.4.0 and v1.8.5 inclusive and the kill_session interface with the ThreadIDs parameter is accessible.
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 Archery to version v1.9.0 or later, which contains the patch for this SQL injection vulnerability in the kill_session interface.
v1.9.0
- Upgrade Archery to version 1.9.0 or later to resolve the SQL injection vulnerability in the kill_session interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38542 — 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-38542 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