📖 ~4 min read • Source: FreeBSD VuXML
VuXML topic: up-imapproxy — multiple vulnerabilities
Related CVEs: CVE-2004-1035
Upstream summary: Timo Sirainen reports: There are various bugs in up-imapproxy which can crash it. Since up-imapproxy runs in a single process with each connection handled in a separate thread, any crash kills all the connections and stops listening for new ones. In 64bit systems it might be possible to make it leak data (mails, passwords, ..) from other connections to attacker's connection. However I don't think up-imapproxy actually works in any 64bit system so this is just a theoretical pr
Table of contents
Symptom & Impact
up-imapproxy runs as a long-lived process on FreeBSD 15, started at boot and holding open sockets (visible in ss -lntp), so a flaw in it stays reachable for as long as the service is up. Exploitation usually means code execution in the daemon’s own security context, memory disclosure from a process holding credentials and cached client data, or a crash that takes the listener down. Workers started before the upgrade keep running the old binary until the service is restarted. up-imapproxy is a genuine long-running service, so restart steps do apply — but confirm the service name first with service -e | grep up-imapproxy, since it often differs from the package name (bind ships named).
Environment & Reproduction
Reproduction targets FreeBSD 15. Confirm with freebsd-version -kru, uname -a, and the installed package via pkg info up-imapproxy and pkg query "%n-%v" up-imapproxy. Capture system state with pkg audit -F and service -e. Trigger the workflow that exposes up-imapproxy 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 up-imapproxy 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: service imapproxy status, tail -100 /var/log/messages, pkg audit -F, pkg version -v up-imapproxy, 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 up-imapproxy for integrity. 5) pkg install -fy up-imapproxy 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 up-imapproxy port revision referenced by FreeBSD VuXML. Typical commands: sudo pkg update, sudo pkg upgrade up-imapproxy (or sudo pkg upgrade -y for the whole system), then sudo service imapproxy restart, and pkg audit to confirm no remaining advisories. For ports tree builders: sudo portsnap fetch update + cd /usr/ports/<cat>/up-imapproxy && 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 up-imapproxy 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 up-imapproxy shows the expected fixed version, service imapproxy status is running, pkg audit returns no advisory for up-imapproxy, tail -50 /var/log/messages shows no errors after restart, and the original reproduction for up-imapproxy 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-up-imapproxy-patch. To revert, run sudo pkg install -f <previous-version> or boot the previous BE via bectl activate pre-up-imapproxy-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 up-imapproxy: 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.
