Skip to content

← Actionable
Medium, CVSS 6.3amended

Arbitrary file write in mindsdb when Extracting Tarballs retrieved from a remote location

CVE-2022-23522GHSA-7x45-phmr-9wqp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mindsdb 22.11.4.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI mindsdb

    Affected
    < 22.11.4.3
    Fixed in
    22.11.4.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N · score source
EPSS
  • CVE-2022-23522: 0.88% estimated exploitation activity in the next 30 days; percentile 59.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary An unsafe extraction is being performed using shutil.unpackarchive() from a remotely retrieved tarball. Which may lead to the writing of the extracted files to an unintended location. This vulnerability is sometimes called a TarSlip or a ZipSlip variant. Details Unpacking files using the high-level function shutil.unpackarchive() from a potentially malicious tarball without validating that the destination file path remained within the intended destination directory may cause files to be overwritten outside the destination directory. As can be seen in the vulnerable snippet code source, an archive is being retrieved using the downloadfile() function from a remote location which is a user-provided permanent storage bucket s3. Immediately after being retrieved, the tarball is unsafely unpacked using the function shutil.unpackarchive(). The vulnerable code is L128..L129 in fs.py file. PoC The following PoC is provided for illustration purposes only. It showcases the risk of…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-7x45-phmr-9wqp

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-7x45-phmr-9wqp

Agent brief

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

# Patch Next advisory brief: CVE-2022-23522

Advisory: Arbitrary file write in mindsdb when Extracting Tarballs retrieved from a remote location
IDs: CVE-2022-23522, GHSA-7x45-phmr-9wqp
Record: https://patchnext.com/advisories/cve-2022-23522 (revision 3, source checked 26 Oct 2026, 13:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mindsdb 22.11.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mindsdb: affected < 22.11.4.3; fixed in 22.11.4.3

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mindsdb.
- 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-7x45-phmr-9wqp (OSV record GHSA-7x45-phmr-9wqp lists affected ranges: PyPI mindsdb >=0 <22.11.4.3 (fixed))
- Verified: https://github.com/advisories/GHSA-7x45-phmr-9wqp (GitHub-reviewed advisory GHSA-7x45-phmr-9wqp lists affected ranges: PyPI mindsdb >=0 <22.11.4.3)

Commands are suggestions: review each one before running it.

Loading voting…