Affected versions: FreeBSD 15

📖 ~4 min read  •  Source: FreeBSD VuXML

VuXML topic: evince and atril — command injection vulnerability in CBT handler

Related CVEs: CVE-2017-1000083

Upstream summary: GNOME reports: The comic book backend in evince 3.24.0 (and earlier) is vulnerable to a command injection bug that can be used to execute arbitrary commands when a CBT file is opened. The same vulnerability affects atril, the Evince fork.

Table of contents
  1. Symptom & Impact
  2. Environment & Reproduction
  3. Root Cause Analysis
  4. Quick Triage
  5. Step-by-Step Diagnosis
  6. Solution – Primary Fix
  7. Solution – Alternative Approaches
  8. Verification & Acceptance Criteria
  9. Rollback Plan
  10. Prevention & Hardening
  11. Related Errors & Cross-Refs
  12. References & Further Reading

Symptom & Impact

Exploitation of atril-lite is user-driven: the danger arrives when someone opens a hostile page, message or attachment, so exposure sits on each FreeBSD 15 workstation rather than on any serving path. Desktop sessions run for weeks, and the package manager only replaces files on disk — a atril-lite process started before the update keeps the old code mapped until the user quits and relaunches it. Consequences are local: theft of saved credentials and session cookies, access to the user’s profile data under $HOME, and code execution as the logged-in account. atril-lite is a graphical application launched by a user from their desktop session, not a system service: there is no service to restart, and service(8) or /var/log/messages will report nothing for it.

Environment & Reproduction

Reproduction targets FreeBSD 15. Confirm with freebsd-version -kru, uname -a, and the installed package via pkg info atril-lite and pkg query "%n-%v" atril-lite. Capture system state with pkg audit -F and service -e. Trigger the workflow that exposes atril-lite 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 atril-lite 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 atril-lite, 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 atril-lite for integrity. 5) pkg install -fy atril-lite 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 atril-lite port revision referenced by FreeBSD VuXML. Typical commands: sudo pkg update, sudo pkg upgrade atril-lite (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>/atril-lite && 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 atril-lite 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 atril-lite shows the expected fixed version is running, pkg audit returns no advisory for atril-lite, tail -50 /var/log/messages shows no errors after restart, and the original reproduction for atril-lite 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-atril-lite-patch. To revert, run sudo pkg install -f <previous-version> or boot the previous BE via bectl activate pre-atril-lite-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 issues that commonly surface alongside atril-lite: 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.