Cache poison in local-unbound service
FreeBSD-SA-25:10.unbound · CVE-2025-11411
Our decision for FreeSense
FreeBSD corrected this on 2025-11-26, before the FreeBSD source pin of every FreeSense version.
- Advisory: corrected 2025-11-26
- FreeSense 1.0 pin: e004ff15f87e (2026-08-03)
- FreeSense 1.1 pin: a52c50b4b7c2 (2026-10-04)
- FreeSense 1.2 pin: a52c50b4b7c2 (2026-10-04)
By FreeSense version
| Version | Status | FreeBSD pin |
|---|---|---|
| FreeSense 1.01.0.7 · frozen, no further fixes | FixedFreeBSD pin of 2026-08-03 | 2026-08-03e004ff15 |
| FreeSense 1.11.1.9 | FixedFreeBSD pin of 2026-10-04 | 2026-10-04a52c50b4 |
| FreeSense 1.21.2.0-DEVELOPMENT | FixedFreeBSD pin of 2026-10-04 | 2026-10-04a52c50b4 |
Workaround
No workaround is available. Systems not leveraging the local-unbound service are unaffected. Check 'sysrc local_unbound_enable' and 'ps ax | grep local-unbound' to see if it is enabled and running.
What FreeBSD says
Promiscuous NS RRSets that complement DNS replies in the authority section can be used to trick resolvers to update their delegation information for the zone. Usually these RRSets are used to update the resolver's knowledge of the zone's name servers. If a malicious actor is able to attach such records in a reply they would be able to poison Unbound's cache for the delegation point.
Impact
A malicious actor can exploit the possible poisonous effect by injecting NS RRSets (and possibly their respective address records) in a reply. This could be done, for example, by trying to spoof a packet or fragmentation attacks. Unbound would then proceed to update the NS RRSet data it already has since the new data has enough trust for it, i.e., in-zone data for the delegation point. FreeBSD 15.0 release candidates previously included a fix to mitigate the poison attempt. This advisory includes an additional fix to mitigate a poison attempt through YXDOMAIN and nodata non-referral answers. This advisory includes patches for FreeBSD 14.3-RELEASE and 13.5-RELEASE that cover both the original
Excerpt from the FreeBSD advisory. Read the original for the full text and the fix.