dbcve.org
ArcheryApplication · Archerydms

CVE-2022-38539

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to after 1.8.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Archery v1.7.5 to v1.8.5 was discovered to contain a SQL injection vulnerability via the where parameter at /archive/apply.

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 confidence

Archery v1.7.5 to v1.8.5 contains a SQL injection vulnerability in the 'where' parameter at the /archive/apply endpoint. An attacker can inject malicious SQL queries through this parameter, potentially allowing unauthorized database access, data exfiltration, or complete system compromise. The CVSS 9.8 indicates the vulnerability is exploitable remotely without authentication.

MitigationUpgrade to a version beyond v1.8.5 if available; otherwise, implement parameterized queries or stored procedures for the affected endpoint and apply input validation on the 'where' parameter.

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
ArcheryApplication
Affected:>= 1.7.5, <= 1.8.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Archery installation and version
    Locate the installed Archery application and determine its version by checking the version file, about page, or administrative interface. Common locations include the application's source directory, Docker image tags, or package management records.
    Affected if The installed version is >= 1.7.5 and <= 1.8.5
  2. Confirm the /archive/apply endpoint exists
    Verify the vulnerable endpoint is accessible by attempting to reach http(s)://<archery-host>/archive/apply or checking the application's URL routing configuration for this path.
    Affected if The /archive/apply endpoint is present and routable in the application
  3. Check application accessibility
    Determine whether the Archery application is exposed to network access. Review firewall rules, reverse proxy configurations, and network ACLs to determine if the application is reachable from untrusted networks.
    Affected if The application is accessible from remote or untrusted network segments without authentication requirements
  4. Verify the 'where' parameter handling
    Review the source code or configuration for the /archive/apply endpoint to confirm the 'where' parameter is processed without parameterized queries or input sanitization. Check the SQL query construction logic in the application's request handlers.
    Affected if The 'where' parameter is used directly in SQL queries without prepared statements, parameter binding, or input validation

If the installed Archery version falls within v1.7.5 to v1.8.5 and the /archive/apply endpoint with its 'where' parameter is accessible without authentication, the environment is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.8.5
Interim mitigation

Upgrade to a version beyond v1.8.5 if available; otherwise, implement parameterized queries or stored procedures for the affected endpoint and apply input validation on the 'where' parameter.

Recommended fix Moderate confidence

Upgrade to Archery version 1.8.6 or later, or to the latest stable release (such as 1.9.0 or beyond)

  1. 1. Back up your current Archery database and configuration files before upgrading.
  2. 2. Check the official Archery GitHub repository (github.com) for the latest stable release version.
  3. 3. Upgrade Archery to version 1.8.6 or later (or the latest stable release beyond 1.8.5) that includes the SQL injection fix.
  4. 4. Verify the /archive/apply endpoint no longer accepts unsanitized SQL input in the 'where' parameter.
  5. 5. Test that normal functionality of the archive application feature continues to work after the upgrade.
Caveat Review release notes for any configuration or database migration requirements between 1.8.5 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archery Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38539 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38539 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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