CVE-2017-6410

kpac/script.cpp in KDE kio before 5.32 and kdelibs before 4.14.30 calls the PAC FindProxyForURL function with a full https URL (potentially including Basic Authentication credentials, a query string, or PATH_INFO), which allows remote attackers to obtain sensitive information via a crafted PAC file.

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

CVE-2017-6410 is rated Moderate Risk (41/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.83%). 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-6410

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-06-15 0.18% 0.83% +0.65%
2 2026-05-15 0.29% 0.18% -0.11%
3 2025-11-21 — 0.29% —

Full EPSS history (11 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N 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:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N 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:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2017-6410

OS Trackers for CVE-2017-6410

vendor priority summary link
debian not yet assigned CVE-2017-6410 not yet assigned priority: Debian including 1 source packages (kio), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-6410
redhat low — https://access.redhat.com/security/cve/CVE-2017-6410
suse medium CVE-2017-6410 severity moderate: SUSE including 30 source package names (kdelibs4-4.14.18-6.2, kdelibs4-4.14.25-5.3, …), 30 product×package rows across 2 product lines (SUSE Package Hub 12 SP1, SUSE Package Hub 12 SP2): Fixed 30. https://www.suse.com/security/cve/CVE-2017-6410/
ubuntu medium CVE-2017-6410 medium priority: Ubuntu including 2 source packages (kde4libs, kio), 10 status rows across 5 suites (precise, trusty, upstream, xenial, yakkety): released 6, DNE 2, needed 2. https://ubuntu.com/security/CVE-2017-6410

Affected software / configurations for CVE-2017-6410

Vendor Product Version Raw CPE
kde kdelibs <= 4.14.29 cpe:2.3:a:kde:kdelibs:*:*:*:*:*:*:*:*
kde kio <= 5.31 cpe:2.3:a:kde:kio:*:*:*:*:*:*:*:*

References for CVE-2017-6410

cvelogic Threat Intelligence