CVE-2017-6309

An issue was discovered in tnef before 1.4.13. Two type confusions have been identified in the parse_file() function. These might lead to invalid read and write operations, controlled by an attacker.

Published: 2017-02-24 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-6309 is rated Moderate Risk (51.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.41%). Review affected assets and schedule 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-6309

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 2025-03-30 0.66% 0.41% -0.25%
2 2025-03-29 0.37% 0.66% +0.29%
3 2025-03-17 — 0.37% —

Full EPSS history (6 records total)

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

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-6309

OS Trackers for CVE-2017-6309

vendor priority summary link
debian not yet assigned CVE-2017-6309 not yet assigned priority: Debian including 1 source packages (tnef), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-6309
gentoo normal CVE-2017-6309: 1 GLSA(s) (201708-02), 1 atom(s) (net-mail/tnef); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-6309
ubuntu medium CVE-2017-6309 medium priority: Ubuntu including 1 source packages (tnef), 6 status rows across 6 suites (precise, trusty, upstream, xenial, yakkety, zesty): released 5, ignored 1. https://ubuntu.com/security/CVE-2017-6309

Affected software / configurations for CVE-2017-6309

Vendor Product Version Raw CPE
tnef_project tnef <= 1.4.12 cpe:2.3:a:tnef_project:tnef:*:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*

References for CVE-2017-6309

cvelogic Threat Intelligence