LiveActive security incident?Get immediate response
CVE Record

CVE-2022-24439: Remote Code Execution (RCE)

All versions of package gitpython are vulnerable to Remote Code Execution (RCE) due to improper user input validation, which makes it possible to inject a maliciously crafted remote URL into the clone command. Exploiting this vulnerability is possible because the library makes external calls to git without sufficient sanitization of input arguments.

HighCVSS 8.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-24439 affects GitPython, a Python library that wraps Git. If an application lets outsiders control a repository URL used for cloning, a crafted URL may cause code execution through GitPython’s external git invocation. This is high impact, but the CVSS vector marks attack complexity as high.

Executive priority

Prioritize remediation for internet-facing workflows, CI/CD systems, and automation that clone user-supplied repositories. The business risk is remote code execution in systems that often hold source code, secrets, and deployment credentials.

Technical view

The issue is improper validation of user-controlled remote URLs passed into GitPython clone functionality. The library makes external calls to git without sufficient sanitization, enabling argument or command injection in affected flows. The source bundle identifies GitPython and references distribution security updates from Fedora, Debian, and Gentoo.

Likely exposure

Exposure is most likely in Python applications, CI systems, automation, or developer portals that use GitPython to clone repositories from URLs supplied by users, partners, tickets, webhooks, or other untrusted sources.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires a vulnerable GitPython clone path and attacker influence over the remote URL. Impact may include confidentiality, integrity, and availability loss if reached.

Researcher notes

Key unknowns in the bundle are exact fixed upstream versions and exploitation in the wild. Validation should focus on reachable clone flows with attacker-controlled remote URLs, not merely package presence. Do not assume every GitPython installation is exploitable.

Mitigation direction

  • Install applicable GitPython or distribution security updates from trusted vendor channels.
  • Identify applications using GitPython to clone remote repositories.
  • Reject or strictly allowlist untrusted repository URLs before cloning.
  • Avoid passing user-controlled clone parameters into GitPython without validation.
  • Check upstream and OS vendor advisories for fixed package versions.

Validation and detection

  • Inventory Python dependencies for GitPython or python-git packages.
  • Search code for GitPython repository clone usage.
  • Trace whether clone URLs can originate from untrusted input.
  • Confirm patched package versions through package manager or dependency lockfiles.
  • Review CI and automation jobs that clone externally supplied repositories.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-24439 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
10Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2022-24439Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aGitPython0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.