gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GitoxideLabs | gitoxide | unaffected |
|
|||||||||
| GitoxideLabs | gitoxide | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Gitoxidelabs | Gitoxide |
|
||||||||||||||||||||
| Gitoxidelabs | Gitoxide |
|
||||||||||||||||||||
| Gitoxidelabs | Gitoxide |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.522% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | gitoxide before 0.52.1 follows symlinks when reading the worktree .gitmodules file, allowing attackers to inject out-of-repository bytes into submodule metadata. Attackers can create a malicious repository with a symlinked .gitmodules pointing outside the repository tree, causing gitoxide to parse arbitrary external files as submodule configuration and expose attacker-controlled name, path, and url values. | |
| Title | gitoxide before 0.52.1 Repository Boundary Violation via symlinked .gitmodules | |
| First Time appeared |
Gitoxidelabs
Gitoxidelabs gitoxide |
|
| Weaknesses | CWE-59 | |
| CPEs | cpe:2.3:a:gitoxidelabs:gitoxide:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Gitoxidelabs
Gitoxidelabs gitoxide |
|
| References |
| |
| Metrics |
cvssV3_1
|