DEBIAN-CVE-2016-8860

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/CVE-2016-8860
Import Source
https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2016-8860.json
JSON Data
https://api.test.osv.dev/v1/vulns/DEBIAN-CVE-2016-8860
Upstream
Published
2017-01-04T20:59:00Z
Modified
2025-09-19T06:21:51Z
Summary
[none]
Details

Tor before 0.2.8.9 and 0.2.9.x before 0.2.9.4-alpha had internal functions that were entitled to expect that buf_t data had NUL termination, but the implementation of or/buffers.c did not ensure that NUL termination was present, which allows remote attackers to cause a denial of service (client, hidden service, relay, or authority crash) via crafted data.

References

Affected packages

Debian:11 / tor

Package

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

Affected ranges

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

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / tor

Package

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

Affected ranges

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

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / tor

Package

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

Affected ranges

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

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:14 / tor

Package

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

Affected ranges

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

Ecosystem specific 

{
    "urgency": "not yet assigned"
}