FKIE_CVE-2024-36105
Vulnerability from fkie_nvd - Published: 2024-05-27 18:15 - Updated: 2026-06-17 07:36| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "dbt-core",
"vendor": "dbt-labs",
"versions": [
{
"status": "affected",
"version": "\u003c 1.6.15"
},
{
"status": "affected",
"version": "\u003e= 1.7.0, \u003c 1.7.15"
},
{
"status": "affected",
"version": "= 1.8.0"
}
]
}
],
"source": "security-advisories@github.com"
},
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:dbt-labs:dbt-core:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "dbt-core",
"vendor": "dbt-labs",
"versions": [
{
"lessThan": "1.6.15",
"status": "affected",
"version": "0",
"versionType": "custom"
},
{
"lessThan": "1.7.15",
"status": "affected",
"version": "1.7.0",
"versionType": "custom"
}
]
},
{
"cpes": [
"cpe:2.3:a:dbt-labs:dbt-core:1.8.0:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "dbt-core",
"vendor": "dbt-labs",
"versions": [
{
"status": "affected",
"version": "1.8.0"
}
]
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications. Prior to versions 1.6.15, 1.7.15, and 1.8.1, Binding to `INADDR_ANY (0.0.0.0)` or `IN6ADDR_ANY (::)` exposes an application on all network interfaces, increasing the risk of unauthorized access. As stated in the Python docs, a special form for address is accepted instead of a host address: `\u0027\u0027` represents `INADDR_ANY`, equivalent to `\"0.0.0.0\"`. On systems with IPv6, \u0027\u0027 represents `IN6ADDR_ANY`, which is equivalent to `\"::\"`. A user who serves docs on an unsecured public network, may unknowingly be hosting an unsecured (http) web site for any remote user/system to access on the same network. The issue has has been mitigated in dbt-core v1.6.15, dbt-core v1.7.15, and dbt-core v1.8.1 by binding to localhost explicitly by default in `dbt docs serve`.\n"
},
{
"lang": "es",
"value": "dbt permite a los ingenieros y analistas de datos transformar sus datos utilizando las mismas pr\u00e1cticas que utilizan los ingenieros de software para crear aplicaciones. Antes de las versiones 1.6.15, 1.7.15 y 1.8.1, el enlace a `INADDR_ANY (0.0.0.0)` o `IN6ADDR_ANY (::)` expone una aplicaci\u00f3n en todas las interfaces de red, lo que aumenta el riesgo de acceso no autorizado. Como se indica en los documentos de Python, se acepta una forma especial para la direcci\u00f3n en lugar de una direcci\u00f3n de host: `\u0027\u0027` representa `INADDR_ANY`, equivalente a `\"0.0.0.0\"`. En sistemas con IPv6, \u0027\u0027 representa `IN6ADDR_ANY`, que equivale a `\"::\"`. Un usuario que entrega documentos en una red p\u00fablica no segura puede, sin saberlo, alojar un sitio web no seguro (http) al que cualquier usuario/sistema remoto pueda acceder en la misma red. El problema se ha mitigado en dbt-core v1.6.15, dbt-core v1.7.15 y dbt-core v1.8.1 vinculando expl\u00edcitamente a localhost de forma predeterminada en \"dbt docsserve\"."
}
],
"id": "CVE-2024-36105",
"lastModified": "2026-06-17T07:36:06.907",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-36105",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-08-21T13:52:53.518603Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-05-27T18:15:10.613",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://cwe.mitre.org/data/definitions/1327.html"
},
{
"source": "security-advisories@github.com",
"url": "https://docs.python.org/3/library/socket.html#socket-families"
},
{
"source": "security-advisories@github.com",
"url": "https://docs.securesauce.dev/rules/PY030"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/commit/0c08d7a19ad1740be3cb0b2e6d9d64f6537176f7"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/issues/10209"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/pull/10208"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/releases/tag/v1.7.15"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/releases/tag/v1.8.1"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/dbt-labs/dbt-core/security/advisories/GHSA-pmrx-695r-4349"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://cwe.mitre.org/data/definitions/1327.html"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://docs.python.org/3/library/socket.html#socket-families"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://docs.securesauce.dev/rules/PY030"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/task/docs/serve.py#L23C38-L23C39"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/commit/0c08d7a19ad1740be3cb0b2e6d9d64f6537176f7"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/issues/10209"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/pull/10208"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.15"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/releases/tag/v1.7.15"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/releases/tag/v1.8.1"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://github.com/dbt-labs/dbt-core/security/advisories/GHSA-pmrx-695r-4349"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-1327"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.