From owner-svn-ports-head@FreeBSD.ORG Thu May 23 08:02:57 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A0FE39F6; Thu, 23 May 2013 08:02:57 +0000 (UTC) (envelope-from cs@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 92209AFC; Thu, 23 May 2013 08:02:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4N82vnJ000231; Thu, 23 May 2013 08:02:57 GMT (envelope-from cs@svn.freebsd.org) Received: (from cs@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4N82v6E000229; Thu, 23 May 2013 08:02:57 GMT (envelope-from cs@svn.freebsd.org) Message-Id: <201305230802.r4N82v6E000229@svn.freebsd.org> From: Carlo Strub Date: Thu, 23 May 2013 08:02:57 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r318851 - head/security/vuxml X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 08:02:57 -0000 Author: cs Date: Thu May 23 08:02:56 2013 New Revision: 318851 URL: http://svnweb.freebsd.org/changeset/ports/318851 Log: fix typo in recent otrs vulnerability Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Thu May 23 07:58:57 2013 (r318850) +++ head/security/vuxml/vuln.xml Thu May 23 08:02:56 2013 (r318851) @@ -87,7 +87,7 @@ Note: Please add new entries to the beg -

SO-AND-SO reports:

+

The OTRS Project reports:

An attacker with permission to write changes, workorder items or FAQ articles could inject JavaScript code into the articles which would be executed by the browser of other users reading the article.