Skip to content
Fencer Intel
critical 9.8

CVE-2014-9706 json

Dulwich Arbitrary code execution via commit with directory path starting with .git

published 2015-03-31 11 y ago modified 2026-06-17 4 mo ago also GHSA-4j5j-58j7-6c3w , PYSEC-2015-34 , EUVD-2015-0019

cvss
9.8
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
5.0%
EPSS 5.0% chance of exploitation in 30 days, percentile 92%
public exploits
0
none known

Summary

The build_index_from_tree function in index.py in Dulwich before 0.9.9 allows remote attackers to execute arbitrary code via a commit with a directory path starting with .git/, which is not properly handled when checking out a working tree.

Patch / fix

  • pypi dulwich 0.9.9, 0.9.10
  • dulwich Debian 14, Debian 13, Debian 12 0.10.1-1

debian advisories DEBIAN-CVE-2014-9706

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-9706 updated cvss 6.0

python-dulwich: arbitrary files allowed to be commited, leading to code execution

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

5.00% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • openwall.com http://www.openwall.com/lists/oss-security/2015/03/21/1 referenced PoC, tagged "exploit" by a source, unverified
  • lists.launchpad.net https://lists.launchpad.net/dulwich-users/msg00827.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi dulwich
<0.9.10
<0.9.9
0.9.10
0.9.9

Classification

Weakness
  • CWE-19 Data Processing Errors

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.