From owner-freebsd-questions@FreeBSD.ORG Tue Jul 2 14:49:16 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 538247F3 for ; Tue, 2 Jul 2013 14:49:16 +0000 (UTC) (envelope-from reggie@busicast.com) Received: from twosensemedia.com (mail.twosensemedia.com [74.165.41.90]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2141194 for ; Tue, 2 Jul 2013 14:49:14 +0000 (UTC) Received: from [74.165.41.91] (HELO S0030153310) by twosensemedia.com (CommuniGate Pro SMTP 5.2.1) with SMTP id 11877150 for freebsd-questions@freebsd.org; Tue, 02 Jul 2013 09:49:08 -0400 X-Vipre-Scanned: 66F28B2F002C3766F28C7C-TDI Message-ID: <7752F38E19D749DD851286B177ABE56C@S0030153310> From: "Reggie Euser" To: Subject: Curl -7.24.0_4 heap corruption Date: Tue, 2 Jul 2013 09:49:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 14:49:16 -0000 We're running FreeBSD 8.3-RELEASE-p3 and portaudit says: Affected package: curl-7.24.0_2 Type of problem: cURL library -- heap corruption in curl_easy_unescape. Reference: http://portaudit.FreeBSD.org/01cf67b3-dc3b-11e2-a6cd-c48508086173.html 1 problem(s) in your installed packages found. You are advised to update or deinstall the affected package(s) immediately. Have updated ports tree, checked UPDATING (nothing on curl since 2010). For last several days, portmaster curl has attempted to install curl-7.24.0_3 - same heap corruption issue. Today, portmaster curl attempted to install curl-7.24.0_4. I thought, great, the port has been updated! Except that the heap corruption issue persists and the update fails. Anyone have any insights into this issue? Thanks!