Skip to content
Fencer Intel
critical 9.8

CVE-2017-16228 json

Dulwich RCE Vulnerability

published 2017-10-29 9 y ago modified 2026-06-17 4 mo ago also GHSA-cwwh-4382-6fwr , PYSEC-2017-12 , EUVD-2017-0027

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.8%
EPSS 3.8% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

Dulwich before 0.18.5, when an SSH subprocess is used, allows remote attackers to execute arbitrary commands via an ssh URL with an initial dash character in the hostname, a related issue to CVE-2017-9800, CVE-2017-12836, CVE-2017-12976, CVE-2017-1000116, and CVE-2017-1000117.

Patch / fix

  • pypi dulwich 0.18.5
  • dulwich Debian 14, Debian 13, Debian 12 0.18.5-1

debian advisories DEBIAN-CVE-2017-16228

  • python-dulwich SLE Module for Public Cloud 12 0.18.5-4.3.1

suse advisories SUSE-SU-2018:2047-1

  • python-dulwich openSUSE Tumbleweed 1.2.7-1.1
  • python-dulwich openSUSE Tumbleweed 0.21.7-1.3

opensuse advisories openSUSE-SU-2026:11190-1openSUSE-SU-2024:14139-1

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-2017-16228 updated cvss 7.8

python-dulwich: Setting SSH arguments from untrusted URLs allows code execution

  • Red Hat OpenStack Platform 11 (Ocata) python-dulwich
    affected: no fix planned “Will not fix”

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

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

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/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.18.5
0.18.5

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.