CVE-2024-53263

Git LFS is a Git extension for versioning large files. When Git LFS requests credentials from Git for a remote host, it passes portions of the host's URL to the `git-credential(1)` command without checking for embedded line-ending control characters, and then sends any credentials it receives back from the Git credential helper to the remote host. By inserting URL-encoded control characters such as line feed (LF) or carriage return (CR) characters into the URL, an attacker may be able to retrieve a user's Git credentials. This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1. There are no workarounds known at this time.

CVSS

No CVSS.

References

Link	Resource
https://github.com/git-lfs/git-lfs/commit/0345b6f816e611d050c0df67b61f0022916a1c90
https://github.com/git-lfs/git-lfs/releases/tag/v3.6.1
https://github.com/git-lfs/git-lfs/security/advisories/GHSA-q6r2-x2cc-vrp7
https://lists.debian.org/debian-lts-announce/2025/01/msg00022.html

Configurations

No configuration.

History

23 Jan 2025, 18:15

Type	Values Removed	Values Added
References		() https://lists.debian.org/debian-lts-announce/2025/01/msg00022.html -
Summary		(es) Git LFS es una extensión de Git para controlar las versiones de archivos grandes. Cuando Git LFS solicita credenciales de Git para un host remoto, pasa partes de la URL del host al comando `git-credential(1)` sin verificar si hay caracteres de control de fin de línea incrustados y luego envía las credenciales que recibe del asistente de credenciales de Git al host remoto. Al insertar caracteres de control codificados en la URL, como caracteres de avance de línea (LF) o retorno de carro (CR), un atacante puede recuperar las credenciales de Git de un usuario. Este problema existe en todas las versiones anteriores y se solucionó en la v3.6.1. Todos los usuarios deben actualizar a la v3.6.1. No se conocen Workarounds en este momento.

14 Jan 2025, 20:15

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-01-14 20:15

Updated : 2025-01-23 18:15

NVD link : CVE-2024-53263

Mitre link : CVE-2024-53263

CVE.ORG link : CVE-2024-53263

JSON object : View

Products Affected

No product.

CWE

CWE-74

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

{"id": "CVE-2024-53263", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"safety": "NOT_DEFINED", "version": "4.0", "recovery": "NOT_DEFINED", "baseScore": 8.5, "automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "ACTIVE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "NONE", "modifiedAttackVector": "NOT_DEFINED", "integrityRequirements": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "availabilityRequirements": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subsequentSystemIntegrity": "NONE", "vulnerableSystemIntegrity": "HIGH", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "confidentialityRequirements": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "subsequentSystemAvailability": "NONE", "vulnerableSystemAvailability": "NONE", "subsequentSystemConfidentiality": "NONE", "vulnerableSystemConfidentiality": "HIGH", "modifiedSubsequentSystemIntegrity": "NOT_DEFINED", "modifiedVulnerableSystemIntegrity": "NOT_DEFINED", "modifiedSubsequentSystemAvailability": "NOT_DEFINED", "modifiedVulnerableSystemAvailability": "NOT_DEFINED", "modifiedSubsequentSystemConfidentiality": "NOT_DEFINED", "modifiedVulnerableSystemConfidentiality": "NOT_DEFINED"}}]}, "published": "2025-01-14T20:15:28.610", "references": [{"url": "https://github.com/git-lfs/git-lfs/commit/0345b6f816e611d050c0df67b61f0022916a1c90", "source": "security-advisories@github.com"}, {"url": "https://github.com/git-lfs/git-lfs/releases/tag/v3.6.1", "source": "security-advisories@github.com"}, {"url": "https://github.com/git-lfs/git-lfs/security/advisories/GHSA-q6r2-x2cc-vrp7", "source": "security-advisories@github.com"}, {"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00022.html", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-74"}]}], "descriptions": [{"lang": "en", "value": "Git LFS is a Git extension for versioning large files. When Git LFS requests credentials from Git for a remote host, it passes portions of the host's URL to the `git-credential(1)` command without checking for embedded line-ending control characters, and then sends any credentials it receives back from the Git credential helper to the remote host. By inserting URL-encoded control characters such as line feed (LF) or carriage return (CR) characters into the URL, an attacker may be able to retrieve a user's Git credentials. This problem exists in all previous versions and is patched in v3.6.1. All users should upgrade to v3.6.1. There are no workarounds known at this time."}, {"lang": "es", "value": "Git LFS es una extensi\u00f3n de Git para controlar las versiones de archivos grandes. Cuando Git LFS solicita credenciales de Git para un host remoto, pasa partes de la URL del host al comando `git-credential(1)` sin verificar si hay caracteres de control de fin de l\u00ednea incrustados y luego env\u00eda las credenciales que recibe del asistente de credenciales de Git al host remoto. Al insertar caracteres de control codificados en la URL, como caracteres de avance de l\u00ednea (LF) o retorno de carro (CR), un atacante puede recuperar las credenciales de Git de un usuario. Este problema existe en todas las versiones anteriores y se solucion\u00f3 en la v3.6.1. Todos los usuarios deben actualizar a la v3.6.1. No se conocen Workarounds en este momento."}], "lastModified": "2025-01-23T18:15:30.630", "sourceIdentifier": "security-advisories@github.com"}