📖 ~4 min read • Source: FreeBSD VuXML
VuXML topic: kio-extras — HTML Thumbnailer automatic remote file access
Related CVEs: CVE-2018-19120
Upstream summary: Albert Astals Cid reports: Various KDE applications share a plugin system to create thumbnails of various file types for displaying in file managers, file dialogs, etc. kio-extras contains a thumbnailer plugin for HTML files. The HTML thumbnailer was incorrectly accessing some content of remote URLs listed in HTML files. This meant that the owners of the servers referred in HTML files in your system could have seen in their access logs your IP address every time the thumbnail
Table of contents
Symptom & Impact
Nothing executes kio-extras on its own; its code runs inside whatever links against or imports it, so the exposed surface on a FreeBSD 15 host is the union of every process that has loaded it — web workers, cron jobs, mail handlers, backup agents. The package manager replaces the files on disk, but processes already running keep the old build mapped, and virtualenvs, vendored copies and container images each carry their own copy, so a host can report itself patched while still running vulnerable code. kio-extras is a library — code loaded by other programs rather than a daemon — so there is no service to restart and service kio-extras will simply report no such service; restart its consumers instead.
Environment & Reproduction
Reproduction targets FreeBSD 15. Confirm with freebsd-version -kru, uname -a, and the installed package via pkg info kio-extras and pkg query "%n-%v" kio-extras. Capture system state with pkg audit -F and service -e. Trigger the workflow that exposes kio-extras while collecting tail -200 /var/log/messages, dmesg -a, and /var/log/pkg.log.
Root Cause Analysis
Root cause is tracked at FreeBSD VuXML. The FreeBSD ports security team shipped a corrective kio-extras port revision; hosts on an outdated build remain exposed. Correlate /var/log/pkg.log with /var/log/messages and kernel state in sysctl kern.lastpid + sysctl kern.osreldate to isolate the change that triggered the failure mode.
Quick Triage
Quick triage: tail -100 /var/log/messages, pkg audit -F, pkg version -v kio-extras, and pfctl -sr (or ipfw list) to confirm firewall posture. For kernel issues: dmesg -a | tail -100 and kldstat.
Step-by-Step Diagnosis
1) service -e to enumerate failed services. 2) tail -F /var/log/messages and dmesg. 3) Validate firewall via pfctl -sr -v or ipfw show. 4) pkg check -B kio-extras for integrity. 5) pkg install -fy kio-extras to reinstall if tampered. 6) Correlate findings with /var/log/pkg.log and FreeBSD VuXML to pin the commit that introduced the regression.
Solution – Primary Fix
Primary fix: install the corrective kio-extras port revision referenced by FreeBSD VuXML. Typical commands: sudo pkg update, sudo pkg upgrade kio-extras (or sudo pkg upgrade -y for the whole system), then and pkg audit to confirm no remaining advisories. For ports tree builders: sudo portsnap fetch update + cd /usr/ports/<cat>/kio-extras && sudo make deinstall reinstall clean. Reboot if the kernel module is involved.
Need help rolling this patch across a FreeBSD fleet? Our IT Solutions & Services team manages FreeBSD jail/bhyve patch windows. Get in touch for a free consultation.
Solution – Alternative Approaches
Alternatives include locking the package with sudo pkg lock kio-extras until vetted, downgrading via pkg install <older-version> from a pinned repo, switching the FreeBSD pkg repository between quarterly and latest in /usr/local/etc/pkg/repos/FreeBSD.conf, isolating the affected service in a jail (iocage/bastille) with stricter firewall rules, or replacing the service with a vendored static build for the period between exposure detection and full rollout.
Verification & Acceptance Criteria
Acceptance: pkg info kio-extras shows the expected fixed version is running, pkg audit returns no advisory for kio-extras, tail -50 /var/log/messages shows no errors after restart, and the original reproduction for kio-extras no longer triggers across two consecutive runs.
Rollback Plan
Capture state with pkg query "%n-%v" > /root/pkg-pre.txt and a ZFS boot-environment snapshot: bectl create pre-kio-extras-patch. To revert, run sudo pkg install -f <previous-version> or boot the previous BE via bectl activate pre-kio-extras-patch && reboot. For kernel/loader changes, drop to the loader prompt and select the previous boot environment.
Prevention & Hardening
Prevent recurrence by scheduling pkg audit -F via periodic.conf (daily_status_security_pkgaudit_enable="YES"), subscribing to freebsd-security-notifications, mirroring through a local pkg repo managed by poudriere, version-pinning sensitive packages with pkg lock, enabling automatic ZFS BE snapshots before upgrades, and monitoring file integrity via mtree or aide. Apply the CIS FreeBSD hardening checklist where applicable and harden jails with allow.* tunables in /etc/jail.conf.
Related Errors & Cross-Refs
Related issues that commonly surface alongside kio-extras: pkg lock contention, mismatched ABI after kernel/userland skew (freebsd-version vs uname -K), pf rule drift, and stale shared-library references after upgrade (pkg check -d).
View all freebsd-15 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Primary reference: FreeBSD VuXML. Supporting docs: FreeBSD Handbook, man pkg, man freebsd-update, man pfctl, man ipfw, man bectl, man periodic.conf, the FreeBSD Security Advisories at security.freebsd.org, and /usr/ports/UPDATING for port-specific notes implicated in this advisory.
