Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8amended

MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding

CVE-2024-24759GHSA-4jcv-vp96-94xr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mindsdb 23.12.4.2), 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.

Add to your agent

Affected packages

  • PyPI mindsdb

    Affected
    < 23.12.4.2
    Fixed in
    23.12.4.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:L · score source
EPSS
  • CVE-2024-24759: 4.94% estimated exploitation activity in the next 30 days; percentile 92.16 (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 DNS rebinding is a method of manipulating resolution of domain names to let the initial DNS query hits an address and the second hits another one. For instance the host make-190.119.176.200-rebind-127.0.0.1-rr.1u.ms would be initially resolved to 190.119.176.200 and the next DNS issue to 127.0.0.1. Please notice the following in the latest codebase: As you can see, during the call to isprivateurl() the initial DNS query would be issued by ip = socket.gethostbyname(hostname) to an IP (public one) and then due to DNS Rebinding, the next GET request would goes to the private one. PoC After running the poc.py with flask installed, consider visiting the following URLs: 1. http://127.0.0.1:5000/checkprivateurl?url=https://www.example.com since it is in the public space, you would get isprivate: false and the GET request would be issued to the www.Example.com website. 3. http://127.0.0.1:5000/checkprivateurl?url=http://localhost:8667, this one the address is private, you would get…

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

    Amended from ghsa record GHSA-4jcv-vp96-94xr

  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-4jcv-vp96-94xr

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-2024-24759

Advisory: MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding
IDs: CVE-2024-24759, GHSA-4jcv-vp96-94xr
Record: https://patchnext.com/advisories/cve-2024-24759 (revision 3, source checked 26 Oct 2026, 13:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mindsdb 23.12.4.2. A vendor fix does not mean a deployment is fixed.

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

## 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-4jcv-vp96-94xr (OSV record GHSA-4jcv-vp96-94xr lists affected ranges: PyPI mindsdb >=0 <23.12.4.2 (fixed))
- Verified: https://github.com/advisories/GHSA-4jcv-vp96-94xr (GitHub-reviewed advisory GHSA-4jcv-vp96-94xr lists affected ranges: PyPI mindsdb >=0 <23.12.4.2)

Commands are suggestions: review each one before running it.

Loading voting…