Cyber Resilience

CVE-2020-27955

Git Large File Storage Project Git Large File Storage 2.12.0

Public PoCHigh EPSS
Published
05 November 2020
Modified
21 November 2024
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.82 99.6th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2020-27955 is a critical-severity Uncontrolled Search Path Element (CWE-427) vulnerability in Git Large File Storage Project Git Large File Storage. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 0.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Git LFS 2.12.0 allows Remote Code Execution.

CWE(s)

Related Threats

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
Exploiting a public-facing Git LFS server enables remote code execution via CWE-427.
T1203 Exploitation for Client Execution Executionconfidence: HIGH
CWE-427 allows an attacker to execute malicious code on the client when a crafted Git LFS repository is cloned.
T1574.008 Path Interception by Search Order Hijacking Stealthconfidence: MEDIUM
CWE-427 indicates a search-order hijacking weakness that can be abused to load attacker-controlled binaries.
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2023-27362Shared CWE-427
CVE-2023-28596Shared CWE-427
CVE-2023-28740Shared CWE-427
CVE-2026-28760Shared CWE-427
CVE-2025-26404Shared CWE-427
CVE-2023-23554Shared CWE-427
CVE-2026-26098Shared CWE-427
CVE-2025-35972Shared CWE-427
CVE-2026-25191Shared CWE-427
CVE-2026-6645Shared CWE-427

Affected Assets

git large file storage project
git large file storage
2.12.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices directly address design of search paths and resource loading.

PR.PS-01 partial match
prevents

Hardened configuration baselines can enforce safe search-path settings and reduce exposure.

PR.PS-05 partial match
prevents

Execution allow-listing can block malicious binaries placed in hijackable search locations.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect uncontrolled search-path issues but does not prevent them by itself.

mitigates

Restricting software installation reduces the chance that an attacker-controlled path element is introduced into the search path.

mitigates

Secure system architecture and engineering principles require explicit control over search paths and resource locations.

prevents

Secure coding practices directly address the use of fixed or controlled search paths that can be influenced by unintended actors.

prevents

Configuration management can enforce approved search-path settings but does not inherently prevent the weakness.

References