Solved Without correcting the vulnerabilities freebsd-update or portsnap and libarchive?

Hello community!

Out of curiosity I found with this report on security and vulnerability in FreeBSD, the article is posted on 2016-10-05, for more information.

https://www.freebsd.org/security/advisories/FreeBSD-SA-16:31.libarchive.asc


Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

=============================================================================
FreeBSD-SA-16:31.libarchive                                 Security Advisory
                                                         The FreeBSD Project

Topic:          Multiple libarchive vulnerabilities

Category:       core
Module:         portsnap
Announced:      2016-10-05
Affects:        All supported versions of FreeBSD.
Corrected:      2016-09-25 22:02:27 UTC (stable/11, 11.0-STABLE)
                2016-09-27 19:36:12 UTC (releng/11.0, 11.0-RELEASE-p1)
                2016-09-25 22:04:02 UTC (stable/10, 10.3-STABLE)
                2016-10-10 07:18:54 UTC (releng/10.3, 10.3-RELEASE-p10)
                2016-10-10 07:18:54 UTC (releng/10.2, 10.2-RELEASE-p23)
                2016-10-10 07:18:54 UTC (releng/10.1, 10.1-RELEASE-p40)

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:https://security.FreeBSD.org/>.

I.   Background

The libarchive(3) library provides a flexible interface for reading and
writing streaming archive files such as tar(1) and cpio(1), and has been the
basis for the FreeBSD implementation of the tar(1) and cpio(1) utilities
since FreeBSD 5.3.

II.  Problem Description

Flaws in libarchive's handling of symlinks and hard links allow overwriting
files outside the extraction directory, or permission changes to a directory
outside the extraction directory.

III. Impact

An attacker who can control freebsd-update's or portsnap's input to tar can
change file content or permisssions on files outside of the update tool's
working sandbox.

IV.  Workaround

No workaround is available.

V.   Solution
 
Look harder. Or just update your system and see the fixes there. You could also subscribe to the freebsd-announce mailing list and have security reports delivered to your virtual door.
 
Back
Top