Security Advisory

CVE-2024-32002: Git Submodule Clone RCE in PLCnext

Last updated:
  • CVE-2024-32002

CVE-2024-32002 is a Git flaw in which a crafted repository with submodules tricks git clone into writing into a .git/ directory and running a hook before the user can inspect the code. NVD scores it 9.0. Update Git to 2.39.4 or a later fixed release, and PLCnext firmware to 2024.0.6 LTS.

Vulnerability summary

CVSS base score

9

Critical severity

EPSS score (FIRST)

29.2%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2024-32002 · Source: NVD

Affected components

ComponentCPEVersion range
Gitcpe:2.3:a:git:git:*:*:*:*:*:*:*:*before 2.39.4, 2.40.0 to 2.40.1, 2.41.0, 2.42.0 to 2.42.1, 2.43.0 to 2.43.3, 2.44.0 and 2.45.0 (NVD); fixed in 2.39.4, 2.40.2, 2.41.1, 2.42.2, 2.43.4, 2.44.1 and 2.45.1 (Git GHSA-8h77-4q3w-gfgv)
Phoenix Contact PLCnext firmware: AXC F 1152, AXC F 2152, AXC F 3152, BPC 9102S, RFC 4072R, RFC 4072S—Firmware below 2024.0.6 LTS; fixed in 2024.0.6 LTS (CERT@VDE VDE-2024-071)
Phoenix Contact EPC 1502 and EPC 1522—Firmware below 2024.0.6 LTS; VDE-2024-071 names no fixed version and points to the download area for the latest firmware (CERT@VDE VDE-2024-071)

What does this mean for affected devices?

The Git project's advisory GHSA-8h77-4q3w-gfgv, published on 2024-05-14, is titled "Recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution". It explains that "repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed." NVD's Primary score is 9.0, CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, with CWE-59 (link following). GitHub, the CNA, uses the same vector and lists CWE-22 (path traversal) and CWE-434; the advisory shows 9.0, while the CVE record states 9.1 for that vector (NVD, CVE record).

Which Git versions are affected and fixed?

The fixes shipped on 2024-05-14 in Git 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2 and 2.39.4. NVD's CPE configuration covers every version before 2.39.4, 2.40.0 to 2.40.1, 2.41.0, 2.42.0 to 2.42.1, 2.43.0 to 2.43.3, 2.44.0 and 2.45.0. The Git advisory's workaround is to disable symbolic link support, for example with git config --global core.symlinks false, and it adds that "it is best to avoid cloning repositories from untrusted sources." Debian fixed the package in 1:2.20.1-2+deb10u9 for buster (DLA-3844-1), 1:2.30.2-1+deb11u3 for bullseye (DLA-3867-1) and 1:2.39.5-0+deb12u1 for bookworm (DSA-5769-1), per the Debian security tracker. Distribution packages carry backported fixes, so compare the package release, not only the upstream version string.

Which Phoenix Contact devices are affected?

Phoenix Contact's advisory VDE-2024-071, published by CERT@VDE on 2024-12-09, covers "multiple Linux component vulnerabilities fixed in latest PLCnext Firmware release 2024.0.6 LTS", and CVE-2024-32002 is one of six CVEs in it. The affected list is firmware below 2024.0.6 LTS on AXC F 1152 (1151412), AXC F 2152 (2404267), AXC F 3152 (1069208), BPC 9102S (1246285), EPC 1502 (1185416), EPC 1522 (1264328), RFC 4072R (1136419) and RFC 4072S (1051328). The CSAF document marks 2024.0.6 LTS as fixed for the six controllers and BPC; for EPC 1502 and EPC 1522 the remediation is to "check download area for latest Firmware update". Phoenix Contact scores the issue 9.0 with the same vector and classifies it as CWE-59. The other five CVEs in the advisory include the OpenSSH race CVE-2024-6387.

What should PLCnext operators do?

Update to PLCnext firmware 2024.0.6 LTS or later, and keep PLCnext Engineer current, which VDE-2024-071 also recommends. Phoenix Contact's general recommendation is to run network-capable devices in closed networks or behind a suitable firewall. Our Phoenix Contact PLCnext and classic line security guide covers the firmware update path, the System Services page and zone design, and lists earlier PLCnext firmware fixes such as CVE-2020-12519. For the classic line, which has no fix for its engineering protocol, see CVE-2019-9201.

Is CVE-2024-32002 exploited?

CVE-2024-32002 is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). FIRST EPSS gives it 0.29234, the 98.2nd percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueThis advisory's weakness class is Path traversal. Our practical guide covers how to detect, fix, verify and disclose it: How to fix path traversal in embedded firmware.

Evidence

  • NVD: [email protected] Primary CVSS 3.1 9.0 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, CWE-59; GitHub ([email protected]) Secondary 9.0 same vector, CWE-22 and CWE-434; CPE git:git before 2.39.4, 2.40.0 to before 2.40.2, 2.41.0, 2.42.0 to before 2.42.2, 2.43.0 to before 2.43.4, 2.44.0, 2.45.0; published 2024-05-14; status Modified, read 2026-11-19. — NVD
  • Git GHSA-8h77-4q3w-gfgv (2024-05-14): recursive clones on case-insensitive filesystems that support symlinks are susceptible to RCE; crafted submodules write into .git/ and plant a hook that runs during the clone; patched in 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, 2.39.4; workaround git config --global core.symlinks false; avoid cloning untrusted repositories; CVSS 9.0. — Git project security advisory
  • CVE record (CNA GitHub_M): published 2024-05-14, CVSS 3.1 base score 9.1 with vector AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, CWE-22 and CWE-434. — CVE.org
  • CERT@VDE VDE-2024-071 (Phoenix Contact, published 2024-12-09, last update 2025-05-22): multiple Linux component vulnerabilities fixed in PLCnext firmware 2024.0.6 LTS; affected firmware <2024.0.6 LTS on AXC F 1152 (1151412), AXC F 2152 (2404267), AXC F 3152 (1069208), BPC 9102S (1246285), EPC 1502 (1185416), EPC 1522 (1264328), RFC 4072R (1136419), RFC 4072S (1051328); CVE-2024-32002 scored 9.0, CWE-59; six CVEs incl. CVE-2024-6387. — CERT@VDE
  • VDE-2024-071 CSAF: fixed 2024.0.6 LTS for AXC F 1152/2152/3152, BPC 9102S, RFC 4072R/4072S; remediation: update to 2024.0.6 LTS, keep PLCnext Engineer up to date, check download area for EPC 1502/EPC 1522; general recommendation: closed networks or suitable firewall. — CERT@VDE CSAF
  • Debian: git fixed in buster 1:2.20.1-2+deb10u9 (DLA-3844-1), bullseye 1:2.30.2-1+deb11u3 (DLA-3867-1), bookworm 1:2.39.5-0+deb12u1 (DSA-5769-1), unstable 1:2.45.1-1. — Debian security tracker
  • Not in the CISA KEV catalog, version 2026.11.18 (1,786 entries), checked 2026-11-19. — CISA KEV
  • EPSS 0.29234, percentile 0.98209, dataset 2026-11-18, read 2026-11-19. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. Git security advisory GHSA-8h77-4q3w-gfgv: Recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution
  3. CVE.org record CVE-2024-32002 (CNA: GitHub)
  4. CERT@VDE VDE-2024-071: Phoenix Contact, Multiple Vulnerabilities in PLCnext Firmware
  5. CERT@VDE CSAF: VDE-2024-071 (machine-readable advisory)
  6. Debian security tracker: CVE-2024-32002
  7. CISA KEV
  8. FIRST EPSS

Frequently asked questions

Which PLCnext firmware fixes CVE-2024-32002?

PLCnext firmware 2024.0.6 LTS. Phoenix Contact lists AXC F 1152, AXC F 2152, AXC F 3152, BPC 9102S, EPC 1502, EPC 1522, RFC 4072R and RFC 4072S below 2024.0.6 LTS as affected; for EPC 1502 and EPC 1522 it points to the download area for the latest firmware (per CERT@VDE VDE-2024-071).

Which Git versions fix CVE-2024-32002?

Git 2.39.4, 2.40.2, 2.41.1, 2.42.2, 2.43.4, 2.44.1 and 2.45.1, all released on 2024-05-14. Debian backported the fix into its buster, bullseye and bookworm packages (per Git GHSA-8h77-4q3w-gfgv and the Debian security tracker).

Is there a workaround for CVE-2024-32002 without updating Git?

Yes. The Git advisory says the attack does not work when symbolic link support is disabled, for example with git config --global core.symlinks false, and advises against cloning repositories from untrusted sources (per Git GHSA-8h77-4q3w-gfgv).

Is CVE-2024-32002 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). FIRST EPSS gives it 0.29234, the 98.2nd percentile, in the 2026-11-18 dataset (per CISA KEV and FIRST EPSS).