jcvi vulnerable to Configuration Injection due to unsanitized user input

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS

• CVE-2023-35932: 1.79% estimated exploitation activity in the next 30 days; percentile 78.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. PoC The vulnerable code snippet is /jcvi/apps/base.py#LL2227C1-L2228C41. Under some circumstances a user input is retrieved and stored within the fullpath variable which reaches the configuration file ~/.jcvirc. I ripped a part of the codebase into a runnable PoC as follows. All the PoC does is call the getpath() function under some circumstances. To run the PoC, you need to remove the config file ~/.jcvirc to emulate the first run, You can notice the random key/value characters vvvvvvvv = zzzzzzzz were successfully injected. Impact 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.

Published by the source

23 Jun 2023, 21:44 UTC

Last modified by the source

10 Sep 2026, 03:49 UTC

Source last checked

26 Oct 2026, 13:12 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x49m-3cw7-gq5q

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x49m-3cw7-gq5q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-35932

Advisory: jcvi vulnerable to Configuration Injection due to unsanitized user input
IDs: CVE-2023-35932, GHSA-x49m-3cw7-gq5q
Record: https://patchnext.com/advisories/cve-2023-35932 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI jcvi: affected <= 1.3.5

## Suggested inspection (read-only)
- `python -m pip show jcvi`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on jcvi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x49m-3cw7-gq5q (OSV record GHSA-x49m-3cw7-gq5q lists affected ranges: PyPI jcvi >=0 <=1.3.5)
- Verified: https://github.com/advisories/GHSA-x49m-3cw7-gq5q (GitHub-reviewed advisory GHSA-x49m-3cw7-gq5q lists affected ranges: PyPI jcvi >=0 <=1.3.5)

Commands are suggestions: review each one before running it.