FKIE_CVE-2024-45305
Vulnerability from fkie_nvd - Published: 2024-09-02 18:15 - Updated: 2026-06-17 07:53| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "gitoxide",
"vendor": "Byron",
"versions": [
{
"status": "affected",
"version": "\u003c 0.10.10"
}
]
}
],
"source": "security-advisories@github.com"
},
{
"affectedData": [
{
"cpes": [
"cpe:2.3:a:byron:gitoxide:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unknown",
"product": "gitoxide",
"vendor": "byron",
"versions": [
{
"lessThan": "0.10.10",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "gix-path is a crate of the gitoxide project dealing with git paths and their conversions. `gix-path` executes `git` to find the path of a configuration file that belongs to the `git` installation itself, but mistakenly treats the local repository\u0027s configuration as system-wide if no higher scoped configuration is found. In rare cases, this causes a less trusted repository to be treated as more trusted, or leaks sensitive information from one repository to another, such as sending credentials to another repository\u0027s remote. In `gix_path::env`, the underlying implementation of the `installation_config` and `installation_config_prefix` functions calls `git config -l --show-origin` and parses the first line of the output to extract the path to the configuration file holding the configuration variable of highest scope. It is believed to be very difficult to exploit this vulnerability deliberately, due to the need either to anticipate a situation in which higher-scoped configuration variables would be absent, or to arrange for this to happen. Although any operating system may be affected, users running Apple Git on macOS are much less likely to be affected. This issue has been addressed in release version 0.10.10. All users are advised to upgrade."
},
{
"lang": "es",
"value": "gix-path es un paquete del proyecto gitoxide que se ocupa de las rutas de Git y sus conversiones. `gix-path` ejecuta `git` para encontrar la ruta de un archivo de configuraci\u00f3n que pertenece a la instalaci\u00f3n de `git`, pero trata por error la configuraci\u00f3n del repositorio local como de todo el sistema si no se encuentra una configuraci\u00f3n de alcance superior. En casos excepcionales, esto hace que un repositorio menos confiable sea tratado como m\u00e1s confiable, o filtra informaci\u00f3n confidencial de un repositorio a otro, como enviar credenciales al control remoto de otro repositorio. En `gix_path::env`, la implementaci\u00f3n subyacente de las funciones `installation_config` e `installation_config_prefix` llama a `git config -l --show-origin` y analiza la primera l\u00ednea de la salida para extraer la ruta al archivo de configuraci\u00f3n que contiene la variable de configuraci\u00f3n de alcance m\u00e1s alto. Se cree que es muy dif\u00edcil explotar esta vulnerabilidad deliberadamente, debido a la necesidad de anticipar una situaci\u00f3n en la que las variables de configuraci\u00f3n de alcance superior estar\u00edan ausentes, o de hacer arreglos para que esto suceda. Aunque cualquier sistema operativo puede verse afectado, los usuarios que ejecutan Apple Git en macOS tienen muchas menos probabilidades de verse afectados. Este problema se ha solucionado en la versi\u00f3n 0.10.10. Se recomienda a todos los usuarios que actualicen la versi\u00f3n."
}
],
"id": "CVE-2024-45305",
"lastModified": "2026-06-17T07:53:59.410",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 2.5,
"baseSeverity": "LOW",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.0,
"impactScore": 1.4,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2024-45305",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-03T13:50:56.774992Z",
"version": "2.0.3"
}
}
]
},
"published": "2024-09-02T18:15:36.657",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://git-scm.com/docs/git-config#SCOPES"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git/mod.rs#L112"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/Byron/gitoxide/blob/12251eb052df30105538fa831e641eea557f13d8/gix-path/src/env/git/mod.rs#L91"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/Byron/gitoxide/security/advisories/GHSA-v26r-4c9c-h3j6"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-706"
}
],
"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.