cvelist/2020/8xxx/CVE-2020-8516.json
2020-02-10 18:01:18 +00:00

82 lines
3.0 KiB
JSON

{
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2020-8516",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "n/a",
"version": {
"version_data": [
{
"version_value": "n/a"
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "** DISPUTED ** The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before attempting to connect to it, which might make it easier for remote attackers to discover circuit information. NOTE: The network team of Tor claims this is an intended behavior and not a vulnerability."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"url": "https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.html",
"refsource": "MISC",
"name": "https://www.hackerfactor.com/blog/index.php?/archives/868-Deanonymizing-Tor-Circuits.html"
},
{
"refsource": "MISC",
"name": "https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.html",
"url": "https://lists.torproject.org/pipermail/tor-dev/2020-February/014147.html"
},
{
"refsource": "MISC",
"name": "https://security-tracker.debian.org/tracker/CVE-2020-8516",
"url": "https://security-tracker.debian.org/tracker/CVE-2020-8516"
},
{
"refsource": "MISC",
"name": "https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.html",
"url": "https://lists.torproject.org/pipermail/tor-dev/2020-February/014146.html"
},
{
"refsource": "MISC",
"name": "https://trac.torproject.org/projects/tor/ticket/33129",
"url": "https://trac.torproject.org/projects/tor/ticket/33129"
}
]
}
}