From owner-svn-ports-all@FreeBSD.ORG Tue Oct 7 21:04:19 2014
Return-Path: Bugzilla Security Advisory An attacker creating a new Bugzilla account can override certain
+ parameters when finalizing the account creation that can lead to the
+ user being created with a different email address than originally
+ requested. The overridden login name could be automatically added
+ to groups based on the group's regular expression setting. During an audit of the Bugzilla code base, several places
+ were found where cross-site scripting exploits could occur which
+ could allow an attacker to access sensitive information. If a new comment was marked private to the insider group, and a flag
+ was set in the same transaction, the comment would be visible to
+ flag recipients even if they were not in the insider group. Search results can be exported as a CSV file which can then be
+ imported into external spreadsheet programs. Specially formatted
+ field values can be interpreted as formulas which can be executed
+ and used to attack a user's computer. Best Practical reports: RT 4.2.0 and above may be vulnerable to arbitrary
+ execution of code by way of CVE-2014-7169, CVE-2014-7186,
+ CVE-2014-7187, CVE-2014-6277, or CVE-2014-6271 --
+ collectively known as "Shellshock." This vulnerability
+ requires a privileged user with access to an RT instance
+ running with SMIME integration enabled; it applies to both
+ mod_perl and fastcgi deployments. If you have already
+ taken upgrades to bash to resolve "Shellshock," you are
+ protected from this vulnerability in RT, and there is no
+ need to apply this patch. This vulnerability has been
+ assigned CVE-2014-7227. Jenkins Security Advisory: This vulnerability allows unauthenticated users
+ with access to Jenkins' HTTP/HTTPS port to mount a DoS attack on
+ Jenkins through thread exhaustion. Anonymous users can test if the user of a specific name exists or
+ not through login attempts. An user with a permission limited
+ to Job/CONFIGURE can exploit this vulnerability to effectively
+ create a new job, which should have been only possible for users
+ with Job/CREATE permission, or to destroy jobs that he/she does not
+ have access otherwise. Users with Overall/READ permission can access arbitrary files in
+ the file system readable by the Jenkins process, resulting in the
+ exposure of sensitive information, such as encryption keys. If a parameterized job has a default value in a password field,
+ that default value gets exposed to users with Job/READ permission.
+ Reflected cross-site scripting vulnerability in Jenkins
+ core. An attacker can navigate the user to a carefully crafted URL
+ and have the user execute unintended actions. Unauthenticated user can execute arbitrary code on Jenkins master
+ by sending carefully crafted packets over the CLI channel. Programs that constitute plugins can be downloaded by anyone with
+ the Overall/READ permission, resulting in the exposure of otherwise
+ sensitive information, such as hard-coded keys in plugins, if
+ any. Security vulnerability in commons fileupload allows
+ unauthenticated attacker to upload arbitrary files to Jenkins
+ master. reflective XSS vulnerability in one of the
+ library dependencies of Jenkins. Monitoring plugin allows an attacker to cause a
+ victim into executing unwanted actions on Jenkins instance. Certain pages in monitoring plugin are visible to anonymous users,
+ allowing them to gain information that they are not supposed to.
+ SECURITY-87 is rated medium, as it results in the
+ loss of functionality. SECURITY-110 is rated medium, as it results in a
+ limited amount of information exposure. SECURITY-127 and SECURITY-128 are rated high. The
+ formed can be used to further escalate privileges, and the latter
+ results inloss of data. SECURITY-131 and SECURITY-138 is rated critical.
+ This vulnerabilities results in exposure of sensitie information
+ and is easily exploitable. SECURITY-143 is rated high. It is a passive
+ attack, but it can result in a compromise of Jenkins master or loss
+ of data. SECURITY-150 is rated critical. This attack can
+ be mounted by any unauthenticated anonymous user with HTTP
+ reachability to Jenkins instance, and results in remote code
+ execution on Jenkins. SECURITY-155 is rated medium. This only affects
+ users who have installed proprietary plugins on publicly accessible
+ instances, which is relatively uncommon. SECURITY-159 is rated critical. This attack can
+ be mounted by any unauthenticated anonymous user with HTTP
+ reachability to Jenkins instance. SECURITY-113 is rated high. It is a passive
+ attack, but it can result in a compromise of Jenkins master or loss
+ of data. Note that this is different than the public "Shellshock"
+ issue. Specially crafted environment variables could lead to remote
+ arbitrary code execution. This was fixed in bash 4.3.27, however
+ the port was patched with a mitigation in 4.3.25_2. The phpMyAdmin development team reports: With a crafted ENUM value it is possible to trigger an
+ XSS in table search and table structure pages. This
+ vulnerability can be triggered only by someone who is
+ logged in to phpMyAdmin, as the usual token protection
+ prevents non-logged-in users from accessing the required
+ pages.
+
+
+ Unauthorized Account Creation
+ Cross-Site Scripting
+ Information Leak
+ Social Engineering
+
+
+
+
+
+
+ Description
+ SECURITY-87/CVE-2014-3661 (anonymous DoS attack through CLI
+ handshake)
+ SECURITY-110/CVE-2014-3662 (User name discovery)
+ SECURITY-127&128/CVE-2014-3663 (privilege escalation in job
+ configuration permission)
+ SECURITY-131/CVE-2014-3664 (directory traversal attack)
+ SECURITY-138/CVE-2014-3680 (Password exposure in DOM)
+ SECURITY-143/CVE-2014-3681 (XSS vulnerability in Jenkins
+ core)
+ SECURITY-150/CVE-2014-3666 (remote code execution from CLI)
+ SECURITY-155/CVE-2014-3667 (exposure of plugin code)
+ SECURITY-159/CVE-2013-2186 (arbitrary file system write)
+ SECURITY-149/CVE-2014-1869 (XSS vulnerabilities in
+ ZeroClipboard)
+ SECURITY-113/CVE-2014-3678 (XSS vulnerabilities in monitoring
+ plugin)
SECURITY-113/CVE-2014-3679 (hole in access control)
+ Severity
+
+
+
+
+An off-by-one error was discovered in the way Bash was handling + deeply nested flow control constructs. Depending on the layout of + the .bss segment, this could allow arbitrary execution of code that + would not otherwise be executed by Bash.
+