DEBIAN-CVE-2017-17458

Source
https://security-tracker.debian.org/tracker/CVE-2017-17458
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2017-17458.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2017-17458
Upstream
Published
2017-12-07T18:29:00Z
Modified
2025-09-19T06:20:32Z
Summary
[none]
Details

In Mercurial before 4.4.1, it is possible that a specially malformed repository can cause Git subrepositories to run arbitrary code in the form of a .git/hooks/post-update script checked into the repository. Typical use of Mercurial prevents construction of such repositories, but they can be created programmatically.

References

Affected packages

Debian:11 / mercurial

Package

Name
mercurial
Purl
pkg:deb/debian/mercurial?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.4.1-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / mercurial

Package

Name
mercurial
Purl
pkg:deb/debian/mercurial?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.4.1-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / mercurial

Package

Name
mercurial
Purl
pkg:deb/debian/mercurial?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.4.1-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:14 / mercurial

Package

Name
mercurial
Purl
pkg:deb/debian/mercurial?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
4.4.1-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}