Skip to main content
No exploitation reportedFix available

CVE-2017-16671

No exploitation reported by the sources we read.

  • Published2017-11-09
  • Fixed in15.1.1 · 14.7.1 · 13.18.1
  • WeaknessCWE-119

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2017-11-0900:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-16671?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-16671?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Digium asterisk
BranchAffectedFixed in
15.x≥ 15.0.0, < 15.1.115.1.1
14.x≥ 14.0.0, < 14.7.114.7.1
13.x≥ 13.0.0, < 13.18.113.18.1
Digium certified asterisk
BranchAffectedFixed in
13.13= 13.13.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Digium asterisk to 15.1.1 · 14.7.1 · 13.18.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.08.8read 2026-10-23
  • NVDCVSS 2.06.5read 2026-10-23
  • NVDweakness (CWE)CWE-119read 2026-10-23
  • FIRST EPSSEPSS score4.2 %2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2017-11-09
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-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 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.

Is CVE-2017-16671 actively exploited?

Active exploitation of CVE-2017-16671 has not been confirmed. Its EPSS score was 4.2% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-16671?

CVE-2017-16671 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month