cve.bz

CVE-2017-16671 digium

8.8 highEPSS 4.2%

High (8.8) in digium. EPSS 4.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

8.8 high
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
4.2% (unchanged from 4.2% a week ago; 4.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-16671 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-16671?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-16671?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-16671 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
digium:asteriskfrom 13.0.0 before 13.18.1
digium:asteriskfrom 14.0.0 before 14.7.1
digium:asteriskfrom 15.0.0 before 15.1.1
digium:certified_asterisk13.13.0
digium:certified_asterisk13.13.0:cert1
digium:certified_asterisk13.13.0:cert1_rc1
digium:certified_asterisk13.13.0:cert1_rc2
digium:certified_asterisk13.13.0:cert1_rc3
digium:certified_asterisk13.13.0:cert1_rc4
digium:certified_asterisk13.13.0:cert2
digium:certified_asterisk13.13.0:cert3
digium:certified_asterisk13.13.0:cert4
digium:certified_asterisk13.13.0:cert5
digium:certified_asterisk13.13.0:cert6

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14asterisk1:13.18.1~dfsg-1DEBIAN-CVE-2017-16671
UbuntuPro:16.04:LTSasterisk1:13.1.0~dfsg-1.1ubuntu4.1+esm1UBUNTU-CVE-2017-16671 USN-4814-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON