CVE-2017-6827

Heap-based buffer overflow in the MSADPCM::initializeCoefficients function in MSADPCM.cpp in audiofile (aka libaudiofile and Audio File Library) 0.3.6 allows remote attackers to have unspecified impact via a crafted audio file.

Published: 2017-03-15 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-6827 is rated Moderate Risk (61.6/100): CVSS High severity, with high exploitation likelihood (EPSS 30.35%, 97th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-6827

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-23 33.78% 30.35% -3.43%
2 2026-02-18 32.12% 33.78% +1.66%
3 2026-02-01 — 32.12% —

Full EPSS history (20 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-6827

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-6827

OS Trackers for CVE-2017-6827

vendor priority summary link
debian not yet assigned CVE-2017-6827 not yet assigned priority: Debian including 1 source packages (audiofile), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-6827
redhat low — https://access.redhat.com/security/cve/CVE-2017-6827
ubuntu medium CVE-2017-6827 medium priority: Ubuntu including 1 source packages (audiofile), 5 status rows across 5 suites (precise, trusty, upstream, xenial, yakkety): released 5. https://ubuntu.com/security/CVE-2017-6827

Affected software / configurations for CVE-2017-6827

Vendor Product Version Raw CPE
audiofile audiofile 0.3.6 cpe:2.3:a:audiofile:audiofile:0.3.6:*:*:*:*:*:*:*

References for CVE-2017-6827

cvelogic Threat Intelligence