CVE-2017-16671
published 2017-11-09CVE-2017-16671: 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…
PriorityP349high8.8CVSS 3.0
AVNACLPRLUINSUCHIHAH
EPSS
3.34%
87.1th percentile
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.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | asterisk | < asterisk 1:13.18.1~dfsg-1 (bullseye) | asterisk 1:13.18.1~dfsg-1 (bullseye) |
| digium | asterisk | >= 0 < 1:13.18.1~dfsg-1 | 1:13.18.1~dfsg-1 |
| digium | asterisk | >= 0 < 1:13.1.0~dfsg-1.1ubuntu4.1+esm1 | 1:13.1.0~dfsg-1.1ubuntu4.1+esm1 |
| digium | asterisk | >= 13.0.0 < 13.18.1 | 13.18.1 |
| digium | asterisk | >= 14.0.0 < 14.7.1 | 14.7.1 |
| digium | asterisk | >= 15.0.0 < 15.1.1 | 15.1.1 |
| digium | certified_asterisk | — | — |
CVSS provenance
nvdv3.08.8HIGHCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.5MEDIUMAV:N/AC:L/Au:S/C:P/I:P/A:P
osv8.8HIGH
vendor_debian8.8HIGH
vendor_ubuntu8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-6vm7-9fw2-vx89: A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13
ghsa_unreviewed·2022-05-14·CVSS 8.8
CVE-2017-16671 [HIGH] CWE-119 GHSA-6vm7-9fw2-vx89: A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13
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.
OSV
asterisk vulnerabilities
osv·2021-03-15·CVSS 8.8
CVE-2017-16671 [HIGH] asterisk vulnerabilities
asterisk vulnerabilities
Richard Mudgett discovered that Asterisk did not properly check the length
of input string when setting the user field for PartyB on a CDR. A remote
attacker could use this vulnerability to cause a denial of service (crash)
or potentially execute arbitrary code. (CVE-2017-16671)
Alex Villacis Lasso discovered that Asterisk did not properly check the
length of input string when setting the user field for PartyA on a CDR. A
remote attacker could use this vulnerability to cause a denial of service
(crash) or potentially execute arbitrary code. (CVE-2017-7617)
OSV
CVE-2017-16671: A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13
osv·2017-11-09·CVSS 8.8
CVE-2017-16671 [HIGH] CVE-2017-16671: A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13
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.
Ubuntu
Asterisk vulnerabilities
vendor_ubuntu·2021-03-15·CVSS 8.8
CVE-2017-7617 [HIGH] Asterisk vulnerabilities
Title: Asterisk vulnerabilities
Summary: Asterisk could be made to crash or run programs if it received specially
crafted input.
Richard Mudgett discovered that Asterisk did not properly check the length
of input string when setting the user field for PartyB on a CDR. A remote
attacker could use this vulnerability to cause a denial of service (crash)
or potentially execute arbitrary code. (CVE-2017-16671)
Alex Villacis Lasso discovered that Asterisk did not properly check the
length of input string when setting the user field for PartyA on a CDR. A
remote attacker could use this vulnerability to cause a denial of service
(crash) or potentially execute arbitrary code. (CVE-2017-7617)
Instructions: In general, a standard system update will make all the necessary changes.
Debian
CVE-2017-16671: asterisk - A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13.18.1...
vendor_debian·2017·CVSS 8.8
CVE-2017-16671 [HIGH] CVE-2017-16671: asterisk - A Buffer Overflow issue was discovered in Asterisk Open Source 13 before 13.18.1...
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.
Scope: local
bullseye: resolved (fixed in 1:13.18.1~dfsg-1)
sid: resolved (fixed in 1:13.18.1~dfsg-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities
bugzilla·2017-11-09·CVSS 8.8
CVE-2017-16671 [HIGH] CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities
CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities
Asterisk Project Security Advisory - AST-2017-009
Buffer overflow in pjproject header parsing can cause crash in Asterisk
By carefully crafting invalid values in the Cseq and the Via header port, pjproject’s packet parsing code can create strings larger than the buffer allocated to hold them. This will usually cause Asterisk to crash immediately. The packets do not have to be authenticated.
http://downloads.asterisk.org/pub/security/AST-2017-009.html
Asterisk Project Security Advisory - AST-2017-010 - CVE-2017-16671
Buffer overflow in CDR's set user
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 th
Bugzilla
CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities [fedora-all]
bugzilla·2017-11-09·CVSS 8.8
CVE-2017-16671 [HIGH] CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities [fedora-all]
CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions
Bugzilla
CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities [epel-6]
bugzilla·2017-11-09·CVSS 8.8
CVE-2017-16671 [HIGH] CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities [epel-6]
CVE-2017-16671 CVE-2017-16672 asterisk: Multiple vulnerabilities [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg u
http://downloads.digium.com/pub/security/AST-2017-010.htmlhttp://www.securityfocus.com/bid/101760https://issues.asterisk.org/jira/browse/ASTERISK-27337https://security.gentoo.org/glsa/201811-11https://www.debian.org/security/2017/dsa-4076http://downloads.digium.com/pub/security/AST-2017-010.htmlhttp://www.securityfocus.com/bid/101760https://issues.asterisk.org/jira/browse/ASTERISK-27337https://security.gentoo.org/glsa/201811-11https://www.debian.org/security/2017/dsa-4076
2017-11-09
Published