dbcve.org
JcviApplication · Jcvi Project

CVE-2023-35932

HIGH · 8.8 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to after 1.3.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
jcvi is a Python library to facilitate genome assembly, annotation, and comparative genomics. A configuration injection happens when user input is considered by the application in an unsanitized format and can reach the configuration file. A malicious user may craft a special payload that may lead to a command injection. The impact of a configuration injection may vary. Under some conditions, it may lead to command injection if there is for instance shell code execution from the configuration file values. This vulnerability does not currently have a fix.

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 · moderate confidence

The jcvi Python library for genome assembly and comparative genomics contains a configuration injection vulnerability where unsanitized user input can reach configuration files. Under certain conditions, this allows attackers to craft malicious payloads in config values that lead to command injection through shell code execution.

MitigationUntil a patch is released, avoid using untrusted or user-controlled input in jcvi configuration files and implement input validation/sanitization at the application layer before passing data to jcvi configuration settings.

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
JcviApplication
Affected:<= 1.3.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
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 checks

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

  1. Identify installed jcvi version
    Run `pip show jcvi` or `pip list | grep jcvi` to display the installed package version
    Affected if Version is 1.3.5 or lower (any version <=1.3.5 is affected)
  2. Locate jcvi configuration files
    Search for `.ini`, `.conf`, or configuration files in the working directory or user home directory, or inspect code that calls jcvi's config loading functions
    Affected if jcvi configuration files exist and are used by the application
  3. Inspect config files for suspicious content
    Examine any configuration files passed to or used by jcvi for shell metacharacters (such as `;`, `|`, `$`, backticks, or `&&`) in value fields
    Affected if Configuration values contain shell metacharacters that could execute arbitrary commands
  4. Trace untrusted input to config usage
    Review application code that populates jcvi configuration values to determine if user-controlled or untrusted data is being written to config files
    Affected if Untrusted or user-supplied data flows into jcvi configuration settings without sanitization

A user is affected if jcvi version is 1.3.5 or lower AND untrusted/user-controlled input is being passed to jcvi configuration values.

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.3.5
Interim mitigation

Until a patch is released, avoid using untrusted or user-controlled input in jcvi configuration files and implement input validation/sanitization at the application layer before passing data to jcvi configuration settings.

Recommended fix High confidence
  1. Since the maintainer has indicated this vulnerability does not currently have a fix, no direct remediation is available through the project.
  2. If you must use jcvi, consider running it in an isolated environment (e.g., container) with minimal privileges to limit the impact of potential command injection.
  3. Review any configuration files passed to jcvi and ensure they are not derived from untrusted user input.
  4. If possible, avoid exposing jcvi functionality to untrusted users or networks.
  5. Monitor the project repository at https://github.com/tanghaibao/jcvi for future security updates.

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

Fix this in Jcvi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35932 — 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-2023-35932 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