mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-07-29 05:56:59 +00:00
78 lines
2.4 KiB
JSON
78 lines
2.4 KiB
JSON
{
|
|
"CVE_data_meta" : {
|
|
"ASSIGNER" : "cve@mitre.org",
|
|
"ID" : "CVE-2017-16671",
|
|
"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" : "A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13.18.1, 14 before 14.7.1, and 15 before 15.1.1 and Certified Asterisk 13.13 before 13.13-cert7. No size checking is done when setting the user field for Party B on a CDR. Thus, it is possible for someone to use an arbitrarily large string and write past the end of the user field storage buffer. NOTE: this is different from CVE-2017-7617, which was only about the Party A buffer."
|
|
}
|
|
]
|
|
},
|
|
"problemtype" : {
|
|
"problemtype_data" : [
|
|
{
|
|
"description" : [
|
|
{
|
|
"lang" : "eng",
|
|
"value" : "n/a"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references" : {
|
|
"reference_data" : [
|
|
{
|
|
"name" : "http://downloads.digium.com/pub/security/AST-2017-010.html",
|
|
"refsource" : "CONFIRM",
|
|
"url" : "http://downloads.digium.com/pub/security/AST-2017-010.html"
|
|
},
|
|
{
|
|
"name" : "https://issues.asterisk.org/jira/browse/ASTERISK-27337",
|
|
"refsource" : "CONFIRM",
|
|
"url" : "https://issues.asterisk.org/jira/browse/ASTERISK-27337"
|
|
},
|
|
{
|
|
"name" : "DSA-4076",
|
|
"refsource" : "DEBIAN",
|
|
"url" : "https://www.debian.org/security/2017/dsa-4076"
|
|
},
|
|
{
|
|
"name" : "101760",
|
|
"refsource" : "BID",
|
|
"url" : "http://www.securityfocus.com/bid/101760"
|
|
}
|
|
]
|
|
}
|
|
}
|