From owner-svn-ports-head@FreeBSD.ORG Tue Mar 26 18:09:07 2013 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 86E9C842; Tue, 26 Mar 2013 18:09:07 +0000 (UTC) (envelope-from delphij@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 78F5C1B7; Tue, 26 Mar 2013 18:09:07 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r2QI97bZ055182; Tue, 26 Mar 2013 18:09:07 GMT (envelope-from delphij@svn.freebsd.org) Received: (from delphij@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r2QI97EF055181; Tue, 26 Mar 2013 18:09:07 GMT (envelope-from delphij@svn.freebsd.org) Message-Id: <201303261809.r2QI97EF055181@svn.freebsd.org> From: Xin LI Date: Tue, 26 Mar 2013 18:09:07 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r315318 - 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: Tue, 26 Mar 2013 18:09:07 -0000 Author: delphij Date: Tue Mar 26 18:09:06 2013 New Revision: 315318 URL: http://svnweb.freebsd.org/changeset/ports/315318 Log: unexpand vuln.xml. Modified: head/security/vuxml/vuln.xml Modified: head/security/vuxml/vuln.xml ============================================================================== --- head/security/vuxml/vuln.xml Tue Mar 26 17:28:33 2013 (r315317) +++ head/security/vuxml/vuln.xml Tue Mar 26 18:09:06 2013 (r315318) @@ -55,12 +55,12 @@ Note: Please add new entries to the beg firebird -- Remote Stack Buffer Overflow - firebird25-server - 2.5.02.5.2 + firebird25-server + 2.5.02.5.2 - firebird21-server - 2.1.02.1.5 + firebird21-server + 2.1.02.1.5 @@ -88,22 +88,22 @@ Note: Please add new entries to the beg optipng -- use-after-free vulnerability - optipng - 0.70.7.4 + optipng + 0.70.7.4 -

Secunia reports:

-
A vulnerability has been reported in OptiPNG, which can be - exploited by malicious people to potentially compromise a user's - system.
-
The vulnerability is caused due to a use-after-free error related - to the palette reduction functionality. No further information is - currently available.
-
Success exploitation may allow execution of arbitrary code.
-

Secunia reports:

+
A vulnerability has been reported in OptiPNG, which can be + exploited by malicious people to potentially compromise a user's + system.
+
The vulnerability is caused due to a use-after-free error related + to the palette reduction functionality. No further information is + currently available.
+
Success exploitation may allow execution of arbitrary code.
+

@@ -200,8 +200,8 @@ Note: Please add new entries to the beg -

libexif project security advisory:

+
libexif project security advisory:
+

A number of remotely exploitable issues were discovered in libexif and exif, with effects ranging from information leakage to potential remote code execution.
@@ -274,8 +274,8 @@ Note: Please add new entries to the beg to cause the master to execute arbitrary code while responding to a catalog request. Specifically, in order to exploit the vulnerability, the puppet master must be made to invoke the - 'template' or 'inline_template' functions during catalog compilation. -
+ 'template' or 'inline_template' functions during catalog compilation. +

A vulnerability found in Puppet could allow an authenticated client to connect to a puppet master and perform unauthorized actions. Specifically, given a valid certificate and private key, an agent @@ -285,8 +285,8 @@ Note: Please add new entries to the beg nodes, facts, and resources. The extent and severity of this vulnerability varies depending on the specific configuration of the master: for example, whether it is using storeconfigs or not, which - version, whether it has access to the cache or not, etc. -
+ version, whether it has access to the cache or not, etc. +

A vulnerability has been found in Puppet which could allow authenticated clients to execute arbitrary code on agents that have been configured to accept kick connections. This vulnerability is @@ -296,27 +296,27 @@ Note: Please add new entries to the beg allow access to the `run` REST endpoint, then a client could construct an HTTP request which could execute arbitrary code. The severity of this issue is exacerbated by the fact that puppet - agents typically run as root. -
+ agents typically run as root. +

A vulnerability has been found in Puppet that could allow a client negotiating a connection to a master to downgrade the master's SSL protocol to SSLv2. This protocol has been found to contain design weaknesses. This issue only affects systems running older versions (pre 1.0.0) of openSSL. Newer versions explicitly disable - SSLv2. -
+ SSLv2. +

A vulnerability found in Puppet could allow unauthenticated clients to send requests to the puppet master which would cause it to load code unsafely. While there are no reported exploits, this vulnerability could cause issues like those described in Rails CVE-2013-0156. This vulnerability only affects puppet masters - running Ruby 1.9.3 and higher. -
+ running Ruby 1.9.3 and higher. +

This vulnerability affects puppet masters 0.25.0 and above. By default, auth.conf allows any authenticated node to submit a report for any other node. This can cause issues with compliance. The - defaults in auth.conf have been changed. -
+ defaults in auth.conf have been changed. +

@@ -358,8 +358,8 @@ Note: Please add new entries to the beg to cause the master to execute arbitrary code while responding to a catalog request. Specifically, in order to exploit the vulnerability, the puppet master must be made to invoke the - 'template' or 'inline_template' functions during catalog compilation. -
+ 'template' or 'inline_template' functions during catalog compilation. +

A vulnerability found in Puppet could allow an authenticated client to connect to a puppet master and perform unauthorized actions. Specifically, given a valid certificate and private key, an agent @@ -369,28 +369,28 @@ Note: Please add new entries to the beg nodes, facts, and resources. The extent and severity of this vulnerability varies depending on the specific configuration of the master: for example, whether it is using storeconfigs or not, which - version, whether it has access to the cache or not, etc. -
+ version, whether it has access to the cache or not, etc. +

A vulnerability has been found in Puppet that could allow a client negotiating a connection to a master to downgrade the master's SSL protocol to SSLv2. This protocol has been found to contain design weaknesses. This issue only affects systems running older versions (pre 1.0.0) of openSSL. Newer versions explicitly disable - SSLv2. -
+ SSLv2. +

A vulnerability found in Puppet could allow an authenticated client to execute arbitrary code on a puppet master that is running in the default configuration, or an agent with `puppet kick` enabled. Specifically, a properly authenticated and connected puppet agent could be made to construct an HTTP PUT request for an authorized report that actually causes the execution of arbitrary code on the - master. -
+ master. +

This vulnerability affects puppet masters 0.25.0 and above. By default, auth.conf allows any authenticated node to submit a report for any other node. This can cause issues with compliance. The - defaults in auth.conf have been changed. -
+ defaults in auth.conf have been changed. +

@@ -416,36 +416,36 @@ Note: Please add new entries to the beg perl -- denial of service via algorithmic complexity attack on hashing routines - perl - 5.12.4_5 - 5.14.05.14.2_3 - 5.16.05.16.2_1 - - - perl-threaded - 5.12.4_5 - 5.14.05.14.2_3 - 5.16.05.16.2_1 + perl + 5.12.4_5 + 5.14.05.14.2_3 + 5.16.05.16.2_1 + + + perl-threaded + 5.12.4_5 + 5.14.05.14.2_3 + 5.16.05.16.2_1 -

Perl developers report:

-
In order to prevent an algorithmic complexity attack - against its hashing mechanism, perl will sometimes - recalculate keys and redistribute the contents of a hash. - This mechanism has made perl robust against attacks that - have been demonstrated against other systems.
-
Research by Yves Orton has recently uncovered a flaw in - the rehashing code which can result in pathological - behavior. This flaw could be exploited to carry out a - denial of service attack against code that uses arbitrary - user input as hash keys.
-
Because using user-provided strings as hash keys is a - very common operation, we urge users of perl to update their - perl executable as soon as possible.
-

Perl developers report:

+
In order to prevent an algorithmic complexity attack + against its hashing mechanism, perl will sometimes + recalculate keys and redistribute the contents of a hash. + This mechanism has made perl robust against attacks that + have been demonstrated against other systems.
+
Research by Yves Orton has recently uncovered a flaw in + the rehashing code which can result in pathological + behavior. This flaw could be exploited to carry out a + denial of service attack against code that uses arbitrary + user input as hash keys.
+
Because using user-provided strings as hash keys is a + very common operation, we urge users of perl to update their + perl executable as soon as possible.
+

@@ -737,9 +737,9 @@ Note: Please add new entries to the beg

low: XSS due to unescaped hostnames CVE-2012-3499

Various XSS flaws due to unescaped hostnames and URIs HTML output in - mod_info, mod_status, mod_imagemap, mod_ldap, and mod_proxy_ftp.
+ mod_info, mod_status, mod_imagemap, mod_ldap, and mod_proxy_ftp.

moderate: XSS in mod_proxy_balancer CVE-2012-4558
-
A XSS flaw affected the mod_proxy_balancer manager interface.
+
A XSS flaw affected the mod_proxy_balancer manager interface.

@@ -831,8 +831,8 @@ Note: Please add new entries to the beg

Unfortnately there is a security vulnerability in Dragonfly when used with Rails which would potentially allow an attacker to run arbitrary code on a host machine using carefully crafted - requests. -

+ requests. +

@@ -883,7 +883,7 @@ Note: Please add new entries to the beg -

The OTRS Project reports:

This advisory covers vulnerabilities discovered in the OTRS core system. This is a variance of the XSS vulnerability, where an attacker @@ -917,7 +917,7 @@ Note: Please add new entries to the beg -
The OTRS Project reports:
+
The OTRS Project reports:

This advisory covers vulnerabilities discovered in the OTRS core system. This is a variance of the XSS vulnerability, where an attacker @@ -952,7 +952,7 @@ Note: Please add new entries to the beg -
The OTRS Project reports:
+
The OTRS Project reports:

This advisory covers vulnerabilities discovered in the OTRS core system. Due to the XSS vulnerability in Internet Explorer an attacker @@ -989,13 +989,13 @@ Note: Please add new entries to the beg

Unrestricted entity expansion can lead to a DoS vulnerability in REXML. (The CVE identifier will be assigned later.) We strongly - recommend to upgrade ruby. -
+ recommend to upgrade ruby. +

When reading text nodes from an XML document, the REXML parser can be coerced in to allocating extremely large string objects which can consume all of the memory on a machine, causing a denial of - service. -
+ service. +

@@ -1047,14 +1047,14 @@ Note: Please add new entries to the beg -
The Django Project reports:
+
The Django Project reports:

These security releases fix four issues: one potential phishing vector, one denial-of-service vector, an information leakage issue, and a range of XML vulnerabilities.
-
+

-
Host header poisoning
+
Host header poisoning

an attacker could cause Django to generate and display URLs that link to arbitrary domains. This could be used as part of a phishing attack. These releases fix this problem by introducing a new @@ -1287,13 +1287,13 @@ Note: Please add new entries to the beg drupal7 -- Denial of service - drupal7 - 7.19 + drupal7 + 7.19 -
Drupal Security Team reports:
+
Drupal Security Team reports:

Drupal core's Image module allows for the on-demand generation of image derivatives. This capability can be abused by requesting @@ -1482,7 +1482,7 @@ Note: Please add new entries to the beg

Today we are proud to announce the release of Rack 1.4.5.

Fix CVE-2013-0263, timing attack against Rack::Session::Cookie
-
Fix CVE-2013-0262, symlink path traversal in Rack::File
+
Fix CVE-2013-0262, symlink path traversal in Rack::File

@@ -1515,11 +1515,11 @@ Note: Please add new entries to the beg
The attr_protected method allows developers to specify a blacklist of model attributes which users should not be allowed to assign to. By using a specially crafted request, attackers could circumvent - this protection and alter values that were meant to be protected.
+ this protection and alter values that were meant to be protected.

All users running an affected release should either upgrade or use one of the work arounds immediately. Users should also consider switching from attr_protected to the whitelist method - attr_accessible which is not vulnerable to this attack.
+ attr_accessible which is not vulnerable to this attack.

@@ -1584,9 +1584,9 @@ Note: Please add new entries to the beg
Multiple cross-site scripting (XSS) vulnerabilities
-
-
Multiple scripts are vulnerable to XSS attacks.
-
+
+
Multiple scripts are vulnerable to XSS attacks.
+
@@ -1630,7 +1630,7 @@ Note: Please add new entries to the beg
When parsing certain JSON documents, the JSON gem can be coerced in to creating Ruby symbols in a target system. Since Ruby symbols are not garbage collected, this can result in a denial of service - attack.
+ attack.

The same technique can be used to create objects in a target system that act like internal objects. These "act alike" objects can be used to bypass certain security mechanisms and can be used as a @@ -1718,20 +1718,20 @@ Note: Please add new entries to the beg OpenSSL -- TLS 1.1, 1.2 denial of service - openssl - 1.0.1_6 + openssl + 1.0.1_6 -
OpenSSL security team reports:
-
-
A flaw in the OpenSSL handling of CBC mode ciphersuites in TLS 1.1 - and TLS 1.2 on AES-NI supporting platforms can be exploited in a +
OpenSSL security team reports:
+
+
A flaw in the OpenSSL handling of CBC mode ciphersuites in TLS 1.1 + and TLS 1.2 on AES-NI supporting platforms can be exploited in a DoS attack.
-
A flaw in the OpenSSL handling of OCSP response verification can - be exploited in a denial of service attack.
-
+
A flaw in the OpenSSL handling of OCSP response verification can + be exploited in a denial of service attack.
+
@@ -1795,22 +1795,22 @@ Note: Please add new entries to the beg opera -- execution of arbitrary code - opera - opera-devel - linux-opera - linux-opera-devel - 12.13 + opera + opera-devel + linux-opera + linux-opera-devel + 12.13 -
Opera reports:
-
-
Particular DOM event manipulations can cause Opera to crash. In - some cases, this crash might occur in a way that allows execution - of arbitrary code. To inject code, additional techniques would - have to be employed.
-
+
Opera reports:
+
+
Particular DOM event manipulations can cause Opera to crash. In + some cases, this crash might occur in a way that allows execution + of arbitrary code. To inject code, additional techniques would + have to be employed.
+
@@ -1993,26 +1993,26 @@ Note: Please add new entries to the beg drupal -- multiple vulnerabilities - drupal6 - 6.28 + drupal6 + 6.28 - drupal7 - 7.19 + drupal7 + 7.19 -
Drupal Security Team reports:
-
-
Cross-site scripting (Various core and contributed modules)
-
Access bypass (Book module printer friendly version)
-
Access bypass (Image module)
-
+
Drupal Security Team reports:
+
+
Cross-site scripting (Various core and contributed modules)
+
Access bypass (Book module printer friendly version)
+
Access bypass (Image module)
+
- https://drupal.org/SA-CORE-2013-001 + https://drupal.org/SA-CORE-2013-001 2013-01-16 @@ -2024,21 +2024,21 @@ Note: Please add new entries to the beg ettercap -- buffer overflow in target list parsing - ettercap - 0.7.4.1 - 0.7.50.7.5.2 + ettercap + 0.7.4.1 + 0.7.50.7.5.2 -
Host target list parsing routine in ettercap - 0.7.4-series prior to 0.7.4.1 and 0.7.5-series - is prone to the stack-based buffer overflow that - may lead to the code execution with the privileges - of the ettercap process.
-
In order to trigger this vulnerability, user or service - that use ettercap should be tricked to pass the crafted list - of targets via the "-j" option.
+
Host target list parsing routine in ettercap + 0.7.4-series prior to 0.7.4.1 and 0.7.5-series + is prone to the stack-based buffer overflow that + may lead to the code execution with the privileges + of the ettercap process.
+
In order to trigger this vulnerability, user or service + that use ettercap should be tricked to pass the crafted list + of targets via the "-j" option.
@@ -2056,79 +2056,79 @@ Note: Please add new entries to the beg java 7.x -- security manager bypass - openjdk7 - 0 + openjdk7 + 0 - linux-sun-jdk - 7.07.11 + linux-sun-jdk + 7.07.11 - linux-sun-jre - 7.07.11 - - - - -
US CERT reports:
-
-
Java 7 Update 10 and earlier versions of Java 7 contain a - vulnerability that can allow a remote, unauthenticated - attacker to execute arbitrary code on a vulnerable - system.
-
The Java JRE plug-in provides its own Security Manager. - Typically, a web applet runs with a security manager - provided by the browser or Java Web Start plugin. Oracle's - document states, "If there is a security manager already - installed, this method first calls the security manager's - checkPermission method with a - RuntimePermission("setSecurityManager") permission to ensure - it's safe to replace the existing security manager. This may - result in throwing a SecurityException".
-
By leveraging the vulnerability in the Java Management - Extensions (JMX) MBean components, unprivileged Java code - can access restricted classes. By using that vulnerability - in conjunction with a second vulnerability involving the - Reflection API and the invokeWithArguments method of the - MethodHandle class, an untrusted Java applet can escalate - its privileges by calling the the setSecurityManager() - function to allow full privileges, without requiring code - signing. Oracle Java 7 update 10 and earlier Java 7 versions - are affected. The invokeWithArguments method was introduced - with Java 7, so therefore Java 6 is not affected.
-
This vulnerability is being attacked in the wild, and is - reported to be incorporated into exploit kits. Exploit code - for this vulnerability is also publicly available.
-
-
Esteban Guillardoy from Immunity Inc. additionally clarifies - on the recursive reflection exploitation technique:
-
-
The real issue is in the native - sun.reflect.Reflection.getCallerClass method.
-
We can see the following information in the Reflection - source code:
-
Returns the class of the method realFramesToSkip frames - up the stack (zero-based), ignoring frames associated with - java.lang.reflect.Method.invoke() and its - implementation.
-
So what is happening here is that they forgot to skip the - frames related to the new Reflection API and only the old - reflection API is taken into account.
-
-
This exploit does not only affect Java applets, but every - piece of software that relies on the Java Security Manager for - sandboxing executable code is affected: malicious code can - totally disable Security Manager.
-
For users who are running native Web browsers with enabled - Java plugin, the workaround is to remove the java/icedtea-web - port and restart all browser instances.
-
For users who are running Linux Web browser flavors, the - workaround is either to disable the Java plugin in browser - or to upgrade linux-sun-* packages to the non-vulnerable - version.
-
It is not recommended to run untrusted applets using - appletviewer, since this may lead to the execution of the - malicious code on vulnerable versions on JDK/JRE.
+ linux-sun-jre + 7.07.11 + + + + +
US CERT reports:
+
+
Java 7 Update 10 and earlier versions of Java 7 contain a + vulnerability that can allow a remote, unauthenticated + attacker to execute arbitrary code on a vulnerable + system.
+
The Java JRE plug-in provides its own Security Manager. + Typically, a web applet runs with a security manager + provided by the browser or Java Web Start plugin. Oracle's + document states, "If there is a security manager already + installed, this method first calls the security manager's + checkPermission method with a + RuntimePermission("setSecurityManager") permission to ensure + it's safe to replace the existing security manager. This may + result in throwing a SecurityException".
+
By leveraging the vulnerability in the Java Management + Extensions (JMX) MBean components, unprivileged Java code + can access restricted classes. By using that vulnerability + in conjunction with a second vulnerability involving the + Reflection API and the invokeWithArguments method of the + MethodHandle class, an untrusted Java applet can escalate + its privileges by calling the the setSecurityManager() + function to allow full privileges, without requiring code + signing. Oracle Java 7 update 10 and earlier Java 7 versions + are affected. The invokeWithArguments method was introduced + with Java 7, so therefore Java 6 is not affected.
+
This vulnerability is being attacked in the wild, and is + reported to be incorporated into exploit kits. Exploit code + for this vulnerability is also publicly available.
+
+
Esteban Guillardoy from Immunity Inc. additionally clarifies + on the recursive reflection exploitation technique:
+
+
The real issue is in the native + sun.reflect.Reflection.getCallerClass method.
+
We can see the following information in the Reflection + source code:
+
Returns the class of the method realFramesToSkip frames + up the stack (zero-based), ignoring frames associated with + java.lang.reflect.Method.invoke() and its + implementation.
+
So what is happening here is that they forgot to skip the + frames related to the new Reflection API and only the old + reflection API is taken into account.
+
+
This exploit does not only affect Java applets, but every + piece of software that relies on the Java Security Manager for + sandboxing executable code is affected: malicious code can + totally disable Security Manager.
+
For users who are running native Web browsers with enabled + Java plugin, the workaround is to remove the java/icedtea-web + port and restart all browser instances.
+
For users who are running Linux Web browser flavors, the + workaround is either to disable the Java plugin in browser + or to upgrade linux-sun-* packages to the non-vulnerable + version.
+
It is not recommended to run untrusted applets using + appletviewer, since this may lead to the execution of the + malicious code on vulnerable versions on JDK/JRE.
@@ -2405,56 +2405,56 @@ Note: Please add new entries to the beg rubygem-rails -- multiple vulnerabilities - rubygem-rails - 3.2.11 + rubygem-rails + 3.2.11 - rubygem-actionpack - 3.2.11 + rubygem-actionpack + 3.2.11 - rubygem-activerecord - 3.2.11 + rubygem-activerecord + 3.2.11 - rubygem-activesupport - 3.2.11 + rubygem-activesupport + 3.2.11 -
Ruby on Rails team reports:
-
-
Two high-risk vulnerabilities have been discovered:
-
(CVE-2013-0155) There is a vulnerability when Active Record is - used in conjunction with JSON parameter parsing.
-
Due to the way Active Record interprets parameters in combination - with the way that JSON parameters are parsed, it is possible for an - attacker to issue unexpected database queries with "IS NULL" or - empty "WHERE" clauses. This issue does not let an attacker insert - arbitrary values into an SQL query, however they can cause the - query to check for NULL or eliminate a WHERE clause when most users - would not expect it.
-
(CVE-2013-0156) There are multiple weaknesses in the parameter - parsing code for Ruby on Rails which allows attackers to bypass - authentication systems, inject arbitrary SQL, inject and execute - arbitrary code, or perform a DoS attack on a Rails application.
-
The parameter parsing code of Ruby on Rails allows applications to - automatically cast values from strings to certain data types. - Unfortunately the type casting code supported certain conversions - which were not suitable for performing on user-provided data - including creating Symbols and parsing YAML. These unsuitable - conversions can be used by an attacker to compromise a Rails - application.
-
+
Ruby on Rails team reports:
+
+
Two high-risk vulnerabilities have been discovered:
+
(CVE-2013-0155) There is a vulnerability when Active Record is + used in conjunction with JSON parameter parsing.
+
Due to the way Active Record interprets parameters in combination + with the way that JSON parameters are parsed, it is possible for an + attacker to issue unexpected database queries with "IS NULL" or + empty "WHERE" clauses. This issue does not let an attacker insert + arbitrary values into an SQL query, however they can cause the + query to check for NULL or eliminate a WHERE clause when most users + would not expect it.
+
(CVE-2013-0156) There are multiple weaknesses in the parameter + parsing code for Ruby on Rails which allows attackers to bypass + authentication systems, inject arbitrary SQL, inject and execute + arbitrary code, or perform a DoS attack on a Rails application.
+
The parameter parsing code of Ruby on Rails allows applications to + automatically cast values from strings to certain data types. + Unfortunately the type casting code supported certain conversions + which were not suitable for performing on user-provided data + including creating Symbols and parsing YAML. These unsuitable + conversions can be used by an attacker to compromise a Rails + application.
+
- CVE-2013-0155 - CVE-2013-0156 - http://weblog.rubyonrails.org/2013/1/8/Rails-3-2-11-3-1-10-3-0-19-and-2-3-15-have-been-released/ - https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-security/t1WFuuQyavI - https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-security/61bkgvnSGTQ + CVE-2013-0155 + CVE-2013-0156 + http://weblog.rubyonrails.org/2013/1/8/Rails-3-2-11-3-1-10-3-0-19-and-2-3-15-have-been-released/ + https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-security/t1WFuuQyavI + https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-security/61bkgvnSGTQ 2013-01-08 @@ -2466,20 +2466,20 @@ Note: Please add new entries to the beg rubygem-rails -- SQL injection vulnerability - rubygem-rails - 3.2.10 + rubygem-rails + 3.2.10 -
Ruby on Rails team reports:
-
-
There is a SQL injection vulnerability in Active Record in ALL - versions. Due to the way dynamic finders in Active Record extract - options from method parameters, a method parameter can mistakenly - be used as a scope. Carefully crafted requests can use the scope - to inject arbitrary SQL.
-
+
Ruby on Rails team reports:
+
+
There is a SQL injection vulnerability in Active Record in ALL + versions. Due to the way dynamic finders in Active Record extract + options from method parameters, a method parameter can mistakenly + be used as a scope. Carefully crafted requests can use the scope + to inject arbitrary SQL.
+
@@ -2513,11 +2513,11 @@ Note: Please add new entries to the beg that may apply to specific installations.

The particular attack vector is only applicable on Jenkins - instances that have slaves attached to them, and allow - anonymous read access.
+ instances that have slaves attached to them, and allow + anonymous read access.
Jenkins allows users to re-generate the API tokens. Those - re-generated API tokens cannot be impersonated by the - attacker.
+ re-generated API tokens cannot be impersonated by the + attacker.

@@ -2535,21 +2535,21 @@ Note: Please add new entries to the beg django -- multiple vulnerabilities - django - 1.4.3 + django + 1.4.3 - django13 - 1.3.5 + django13 + 1.3.5 -
The Django Project reports:
+
The Django Project reports:

-
-
-
Host header poisoning
+
+
+
Host header poisoning

Several earlier Django security releases focused on the issue of poisoning the HTTP Host header, causing Django to generate URLs pointing to arbitrary, potentially-malicious domains.
@@ -2566,9 +2566,9 @@ Note: Please add new entries to the beg
Any deviation from this will now be rejected, raising the exception django.core.exceptions.SuspiciousOperation.
-
-
-
Redirect poisoning
+
+
+
Redirect poisoning

Also following up on a previous issue: in July of this year, we made changes to Django's HTTP redirect classes, performing additional validation of the scheme of the URL to redirect to (since, both @@ -2591,8 +2591,8 @@ Note: Please add new entries to the beg authentication system -- which allow user-supplied redirect targets now use is_safe_url to validate the supplied URL.

-
-
+ +
@@ -2773,20 +2773,20 @@ Note: Please add new entries to the beg
puppet -- multiple vulnerabilities

-
Arbitrary file read on the puppet master from authenticated clients (high). It is possible to construct an HTTP get request from an authenticated client with a valid certificate that will return the contents of an arbitrary file on the Puppet master that the master has read-access to.
-
Arbitrary file delete/D.O.S on Puppet Master from authenticated clients (high). Given a Puppet master with the "Delete" directive allowed in auth.conf for an authenticated host, an attacker on that host can send a specially crafted Delete request that can cause an arbitrary file deletion on the Puppet master, potentially causing a denial of service attack. Note that this vulnerability does *not* exist in Puppet as configured by default.
-
Insufficient input validation for agent hostnames (low). An attacker could trick the administrator into signing an attacker's certificate rather than the intended one by constructing specially crafted certificate requests containing specific ANSI control sequences. It is possible to use the sequences to rewrite the order of text displayed to an administrator such that display of an invalid certificate and valid certificate are transposed. If the administrator signs the attacker's certificate, the attacker can then man-in-the-middle the agent.
+
Arbitrary file read on the puppet master from authenticated clients (high). It is possible to construct an HTTP get request from an authenticated client with a valid certificate that will return the contents of an arbitrary file on the Puppet master that the master has read-access to.
+
Arbitrary file delete/D.O.S on Puppet Master from authenticated clients (high). Given a Puppet master with the "Delete" directive allowed in auth.conf for an authenticated host, an attacker on that host can send a specially crafted Delete request that can cause an arbitrary file deletion on the Puppet master, potentially causing a denial of service attack. Note that this vulnerability does *not* exist in Puppet as configured by default.
+
Insufficient input validation for agent hostnames (low). An attacker could trick the administrator into signing an attacker's certificate rather than the intended one by constructing specially crafted certificate requests containing specific ANSI control sequences. It is possible to use the sequences to rewrite the order of text displayed to an administrator such that display of an invalid certificate and valid certificate are transposed. If the administrator signs the attacker's certificate, the attacker can then man-in-the-middle the agent.

- CVE-2012-3864 - CVE-2012-3865 - CVE-2012-3867 - http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#2.6.17 - http://puppetlabs.com/security/cve/cve-2012-3864/ - http://puppetlabs.com/security/cve/cve-2012-3865/ - http://puppetlabs.com/security/cve/cve-2012-3867/ + CVE-2012-3864 + CVE-2012-3865 + CVE-2012-3867 + http://projects.puppetlabs.com/projects/puppet/wiki/Release_Notes#2.6.17 + http://puppetlabs.com/security/cve/cve-2012-3864/ + http://puppetlabs.com/security/cve/cve-2012-3865/ + http://puppetlabs.com/security/cve/cve-2012-3867/ 2012-07-10 @@ -2889,25 +2889,25 @@ executed in your Internet Explorer while squid -- denial of service - squid - 3.1.23 - 3.23.2.6 - 3.33.3.0.3 + squid + 3.1.23 + 3.23.2.6 + 3.33.3.0.3 -
Squid developers report:
-
-
Due to missing input validation Squid cachemgr.cgi tool - is vulnerable to a denial of service attack when processing - specially crafted requests.
-
This problem allows any client able to reach the - cachemgr.cgi to perform a denial of service attack on the - service host.
-
The nature of the attack may cause secondary effects - through resource consumption on the host server.
-
+
Squid developers report:
+
+
Due to missing input validation Squid cachemgr.cgi tool + is vulnerable to a denial of service attack when processing + specially crafted requests.
+
This problem allows any client able to reach the + cachemgr.cgi to perform a denial of service attack on the + service host.
+
The nature of the attack may cause secondary effects + through resource consumption on the host server.
+
@@ -2926,24 +2926,24 @@ executed in your Internet Explorer while opera -- execution of arbitrary code - opera - opera-devel - linux-opera - linux-opera-devel - 12.12 + opera + opera-devel + linux-opera + linux-opera-devel + 12.12 -
Opera reports:
-
-
When loading GIF images into memory, Opera should allocate the - correct amount of memory to store that image. Specially crafted - image files can cause Opera to allocate the wrong amount of memory. - Subsequent data may then overwrite unrelated memory with - attacker-controlled data. This can lead to a crash, which may also - execute that data as code.
-
+
Opera reports:
+
+
When loading GIF images into memory, Opera should allocate the + correct amount of memory to store that image. Specially crafted + image files can cause Opera to allocate the wrong amount of memory. + Subsequent data may then overwrite unrelated memory with + attacker-controlled data. This can lead to a crash, which may also + execute that data as code.
+
@@ -3042,11 +3042,11 @@ executed in your Internet Explorer while -
The Apache Software Foundation reports:
-
+
The Apache Software Foundation reports:
+

The CSRF prevention filter could be bypassed if a request was made to a protected resource without a session identifier present in the request.
-
+
@@ -3074,12 +3074,12 @@ executed in your Internet Explorer while -
The Apache Software Foundation reports:
-
+
The Apache Software Foundation reports:
+

When using the NIO connector with sendfile and HTTPS enabled, if a client breaks the connection while reading the response an infinite loop is entered leading to a denial of service.
-
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***