--- /dev/null
+{%extends "base/page.html"%}
+{%block title%}Google Summer of Code Program{%endblock%}
+{%block contents%}
+
+<div id="CONTENTWRAP">
+<h1>PostgreSQL and Google Summer of Code</h1>
+
+<p>The PostgreSQL Project is participating in the Google <a
+href="http://socghop.appspot.com/">Summer of Code 2010</a> program. This program endeavors to fund students to contribute to an open source project over the summer break.</p>
+
+<ul>
+<li><a href="#ideas">Example Proposal Ideas</a>
+
+<ul>
+
+<li><a href="#todo">Core Code / TODO Items</a></li>
+
+<li><a href="#infrastructure">Infrastructure</a></li>
+
+<li><a href="#extapps">External Applications</a></li>
+</ul>
+</li>
+
+<li><a href="#mentors">Possible Mentors</a></li>
+
+<li><a href="#proposals">Proposal Guidelines</a></li>
+
+<li><a href="#past">Previously Accepted Projects</a></li>
+
+<li><a href="#faq">Frequently Asked Questions</a></li>
+</ul>
+
+<a id="ideas" name="ideas"></a>
+<h2>Example Proposal Ideas</h2>
+<p>The PostgreSQL Project has a wide range of opinions on what it feels are acceptable GSoC projects. The examples listed here are meant only as a suggestion of things we would likely find useful, but you should not feel obligated to pick from this list by any means. If you have just discovered a new algorithm as part of your thesis work, we would love to see a proposal implementing that in PostgreSQL. The point is that all proposals will be evaluated on their own merits, so be creative.
+
+<a id="todo" name="todo"></a>
+<h3>Core Source Code</h3>
+<ul>
+<li><strong>TODO Items</strong>: A number of the items on our TODO list have been marked as good projects for beginners who are new to the PostgreSQL code. Items on this list have the advantage of already having general community agreement that the feature is desireable. These items should also have some general discussion available in the mailing list archives to help get you started. You can find these items on the <a href="http://wiki.postgresql.org/wiki/Todo">TODO</a> list, they will be marked with an [E].
+</li>
+<li><strong>DDL Functions</strong>: Create a SQL-callable function capable of generating DDL scripts for objects within the database.</li>
+<li><strong>EXPLAIN Enhancements</strong>: Add information to EXPLAIN documenting I/O activity, discarded plans, costing detail, memory usage and more.</li>
+<li><strong>Text-Array Indexing</strong>: Add support for indexing text or multi-typed array data, capable of supporting indexed queries, similar to intarray.</li>
+</ul>
+
+<a id="infrastructure" name="infrastructure"></a>
+<h3>Infrastructure</h3>
+<ul>
+<li><strong>Enhance Buildfarm to test external packages, patches, or performance</strong>: The PostgreSQL project maintains a public buildfarm that continuously communicates with several machines that checkout and build the PostgreSQL source on a regular basis. The idea behind this project is to extend the current buildfarm code to allow it download external modules and report back on their build status, to download unapplied patches and test them, or to run performance tests. </li>
+<li><strong>Create "Performance-Farm" framework for continuous performance regression testing</strong>: Similar to the buildfarm, the idea behind this project is to create a public infrastructure that continuously communicates with several machines that checkout and build the PostgreSQL source on a regular basis, running and reporting on agreed performance benchmarks. </li>
+</ul>
+
+<a id="extapps" name="extapps"></a>
+<h3>External Applications</h3>
+<ul>
+<li><strong>pgAdmin III / phpPgAdmin Enhancements</strong>: PostgreSQL supports a number of popular GUI Tools that are not distributed with the core project. Projects like these often have their own TODO lists and compatibility issues with the core PotgreSQL that need development. We welcome ideas for these projects as well.</li>
+<li><strong>Procedural Language Improvements</strong>: PostgreSQL provides support for more than a dozen different procedural languages, however the level of support varies depending on the language implementation. Enhancing support of these procedural languages might include fixing build issues, adding SPI support, adding trigger support, adding support for IN/OUT parameters and more.</li>
+<li><strong>Replication</strong>: PostgreSQL provides a wide range of replication solutions for varying types of replication needs. Many of these projects need assistance with building against different versions of PostgreSQL, installation and setup, administrative tools, and general bugfixing.</li>
+<li><strong>Teaching & Learning Tools</strong>: External tools to help in teaching the internals of PostgreSQL such as enhanced visual EXPLAIN, graphical models of the query engine, educational guides to the code, and interactive tools to demonstrate various query types.
+<li><strong>PostGIS & GEOS</strong>: Add performance and feature enhancements to PostgreSQL's geographic data support.</li>
+</ul>
+<p>Additional projects may be found by browsing the <a href="http://projects.postgresql.org">PostgreSQL Development Projects</a> website.</p>
+
+<a id="mentors" name="mentors"></a>
+<h2>Mentors</h2>
+
+<p>PostgreSQL follows an open community development model, so student projects are likely to be reviewed and commented on by any and all members of the PostgreSQL community. This also means that we may be able to find mentors for additional projects by reaching out to this community. If you are interested in working on a project not explicitly mentioned above, you may want to contact one of the Summer of Code liaisons below about writing a proposal.</p>
+
+
+<ul>
+ <li>Robert Treat <xzilla @t users.sourceforge.net>, OmniTI Inc., PHP-based projects and infrastructure</li>
+ <li>Selena Deckelmann <selenamarie @t gmail.com>, End Point Inc., user groups and applications</li>
+ <li>Dave Page <dpage @t pgadmin.org>, EnterpriseDB, pgAdmin, GUI tools, and Windows</li>
+</ul>
+
+<p>If your project is not selected for funding by Google, but you still think you have a
+feasible project proposal, then please email our developers mailing list at <a
+href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>.</p>
+
+<a id="proposals" name="proposals"></a>
+
+<h2>Proposal Guidelines</h2>
+
+<p><a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#student_apply">Apply to Summer of Code</a></p>
+
+<p>Students are responsible for writing a proposal and submitting it to Google before the
+application deadline. The following outline was adapted from the Perl Foundation <a
+href="http://www.perlfoundation.org/how_to_write_a_proposal">open source proposal
+HOWTO</a>. A strong proposal will include:</p>
+
+<ul>
+<li><strong>Benefits to the PostgreSQL Community</strong> - a good project will not just be
+fun to work on, but also generally useful to others.</li>
+
+<li><strong>Deliverables</strong> - It is very important to list quantifiable results
+here</li>
+
+<li><strong>Project Schedule</strong> - How long will the project take? When can you
+begin work?</li>
+
+<li><strong>Bio</strong> - Who are you? What makes you the best person to work on this
+project?</li>
+
+<li><strong>Contact</strong> - How can we contact if we have questions about your project?
+Can you supply us with an email/IM/phone method for being contacted, in case of emergency?</li>
+</ul>
+
+<p>Please also see our additional <a href="/developer/summerofcodeadvice">Advice to Students</a> <strong>before</strong> submitting a proposal.</p>
+
+<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vet their proposal with community developers before submitting their proposal to Google SoC. This is not required, but can have a large impact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may affect this, please explain them up front in your proposal.</p>
+
+<a id="past" name="past"></a>
+<h2>Previously Accepted Projects</h2>
+<ul>
+ <li>Enhanced Aggregate Support</li>
+ <li>Full Disjunctions</li>
+ <li>Hashing DISTINCT Clause Implementation</li>
+ <li>ECPG Cleanup</li>
+ <li>Initial support of XMLType for PostgreSQL </li>
+ <li>phpPgAdmin FTS support and other improvements</li>
+ <li>pgAdmin graphical query tool and TSQL-like client scripting support</li>
+ <li>xlog viewer</li>
+</ul>
+
+<p>More information on these projects can be found on Google's PostgreSQL SoC pages: (<a href="http://code.google.com/soc/2008/postgres/about.html">2008</a> | <a href="http://code.google.com/soc/2008/postgres/about.html">2007</a> | <a href="http://code.google.com/soc/2006/pgsql/about.html">2006</a>)</p>
+
+
+<a id="faq" name="faq"></a>
+
+<h2>Frequently Asked Questions</h2>
+
+<ul>
+<li>
+<p><strong>Am I eligible?</strong></p>
+
+<p>Please see the Google <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#eligibility">Eligibility FAQ</a> for all questions about eligibility.</p>
+
+</li>
+
+<li>
+<p><strong>When is the proposal deadline?</strong></p>
+
+<p>According to the <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline">Summer of Code FAQ</a>, the deadline for submitting student proposals is April 9th, 2010 (19:00 UTC). Please remember that proposals must submitted to Google themselves<!-- (via the <a href="http://code.google.com/soc/student_step1.html">student application form</a>) -->, although we are happy to discuss any proposals with you ahead of time.</p>
+</li>
+
+</ul>
+</div>
+{%endblock%}
</p>
<p>
+
The PostgreSQL Global Development Group (PGDG) takes security seriously,
allowing our users to place their trust in the web sites and applications
built around PostgreSQL. Our approach covers fail-safe configuration options,
Vulnerabilities list which major releases they were present
in, and which version they are fixed in for each. If the vulnerability
was exploitable without a valid login, this is also stated. They also
-list a severity, but we urge all users to read the description
+list a vulnerability class, but we urge all users to read the description
to determine if the bug affects specific installations or not.
</p>
<tr>
<th class="colFirst">Reference</th>
<th class="colMid">Affected<br/>versions</th>
+
<th class="colMid">Fixed in</th>
<th class="colMid"><a href="#comp">Component</a></th>
- <th class="colMid"><a href="#sec">Sev</a></th>
+ <th class="colMid"><a href="#cls">Class</a></th>
<th class="colLast">Description</th>
</tr>
+ <tr valign="top">
+
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1169">CVE-2010-1169</a></td>
+ <td class="colMid">8.4, 8.3, 8.2, 8.1, 8.0, 7.4</td>
+ <td class="colMid">8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29</td>
+ <td class="colMid">core server, limited deployments</td>
+ <td class="colMid">C</td>
+ <td class="colLast">A vulnerability in Safe.pm and PL/Perl can allow an authenticated user to run arbitrary Perl code on the database
+ server if PL/Perl is installed and enabled.</td>
+
+ </tr>
+
+ <tr valign="top">
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-1170">CVE-2010-1170</a></td>
+ <td class="colMid">8.4, 8.3, 8.2, 8.1, 8.0, 7.4</td>
+ <td class="colMid">8.4.4, 8.3.11, 8.2.17, 8.1.21, 8.0.25, 7.4.29</td>
+ <td class="colMid">core server, limited deployments</td>
+
+ <td class="colMid">C</td>
+ <td class="colLast">Insecure permissions on the pltcl_modules table could allow an authenticated user to run arbitrary Tcl code on the
+ database server if PL/Tcl is installed and enabled.</td>
+ </tr>
+
+ <tr valign="top">
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4034">CVE-2009-4034</a></td>
+ <td class="colMid">8.4, 8.3, 8.2, 8.1, 8.0, 7.4</td>
+
+ <td class="colMid">8.4.2, 8.3.9, 8.2.15, 8.1.19, 8.0.23, 7.4.27</td>
+ <td class="colMid">client, core server, limited deployments</td>
+ <td class="colMid">A</td>
+ <td class="colLast">NULL Bytes in SSL Certificates can be used to falsify client or server authentication. This only affects users who have SSL enabled, perform certificate name validation or client certificate authentication, and where the Certificate Authority (CA) has been tricked into issuing invalid certificates. The use of a CA that can be trusted to always issue valid certificates is recommended to ensure you are not vulnerable to this issue.</td>
+ </tr>
+
+ <tr valign="top">
+
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4136">CVE-2009-4136</a></td>
+ <td class="colMid">8.4, 8.3, 8.2, 8.1, 8.0, 7.4</td>
+ <td class="colMid">8.4.2, 8.3.9, 8.2.15, 8.1.19, 8.0.23, 7.4.27</td>
+ <td class="colMid">core server</td>
+ <td class="colMid">C</td>
+ <td class="colLast">Privilege escalation via changing session state in an index function. This closes a corner case related to vulnerabilities CVE-2009-3230 and CVE-2007-6600 (below).</td>
+
+ </tr>
+
+ <tr valign="top">
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3229">CVE-2009-3229</a></td>
+ <td class="colMid">8.4, 8.3, 8.2</td>
+ <td class="colMid">8.4.1, 8.3.8, 8.2.14</td>
+ <td class="colMid">core server</td>
+
+ <td class="colMid">D</td>
+ <td class="colLast">Authenticated non-superusers can shut down the backend server by re-LOAD-ing libraries in $libdir/plugins, if any libraries are present there.</td>
+ </tr>
+
+ <tr valign="top">
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3230">CVE-2009-3230</a></td>
+ <td class="colMid">8.4, 8.3, 8.2, 8.1, 8.0, 7.4</td>
+
+ <td class="colMid">8.4.1, 8.3.8, 8.2.14, 8.1.18, 8.0.22, 7.4.26</td>
+ <td class="colMid">core server</td>
+ <td class="colMid">C</td>
+ <td class="colLast">The fix for issue CVE-2007-6600 (below) failed to include protection against misuse of RESET SESSION AUTHORIZATION.</td>
+ </tr>
+
+ <tr valign="top">
+
+ <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3231">CVE-2009-3231</a></td>
+ <td class="colMid">8.3, 8.2</td>
+ <td class="colMid">8.3.8, 8.2.14</td>
+ <td class="colMid">core server</td>
+ <td class="colMid">A</td>
+ <td class="colLast">If PostgreSQL is configured with LDAP authentication, and your LDAP configuration allows anonymous binds, it is possible for a user to authenticate themselves with an empty password.</td>
+
+ </tr>
+
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0922">CVE-2009-0922</a></td>
<td class="colMid">8.3, 8.2, 8.1, 8.0, 7.4</td>
<td class="colMid">8.3.7, 8.2.13, 8.1.17, 8.0.21, 7.4.25</td>
<td class="colMid">core server</td>
+
<td class="colMid">D</td>
<td class="colLast">It is possible to cause a momentary denial of service when there is a failure to convert a localized error message to the client-specified encoding. A valid login is required to exploit this vulnerability.</td>
</tr>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6600">CVE-2007-6600</a><br/><a href="/about/news.905">Announcement</a></td>
<td class="colMid">8.2, 8.1, 8.0, 7.4, 7.3</td>
+
<td class="colMid">8.2.6, 8.1.11, 8.0.15, 7.4.19, 7.3.21</td>
<td class="colMid">core server</td>
<td class="colMid">C</td>
</tr>
<tr valign="top">
+
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4769">CVE-2007-4769</a><br/><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4772">CVE-2007-4772</a><br/><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6067">CVE-2007-6067</a><br/><a href="/about/news.905">Announcement</a></td>
<td class="colMid">8.2, 8.1, 8.0, 7.4</td>
<td class="colMid">8.2.6, 8.1.11, 8.0.15, 7.4.19</td>
<td class="colMid">core server</td>
<td class="colMid">B</td>
+
<td class="colLast">Three vulnearbilities in the regular expression handling libraries can be exploited to cause a backend crash, infinite loops or memory exhaustion. This vulnearbility can be exploited through frontend applications that allow unfiltered regular expressions to be passed in queries.</td>
</tr>
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6601">CVE-2007-6601</a><br/><a href="/about/news.905">Announcement</a></td>
<td class="colMid">8.2, 8.1, 8.0, 7.4, 7.3</td>
<td class="colMid">8.2.6, 8.1.11, 8.0.15, 7.4.19, 7.3.21</td>
+
<td class="colMid">contrib module</td>
<td class="colMid">C</td>
<td class="colLast">DBLink functions combined with local trust or ident access control could be used by a malicious user togain superuser privileges. A valid login is required to exploit this vulnerability.</td>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2138">CVE-2007-2138</a><br/><a href="/about/news.791">Announcement</a></td>
+
<td class="colMid">8.2, 8.1, 8.0, 7.4, 7.3</td>
<td class="colMid">8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19</td>
<td class="colMid">core server</td>
<td class="colMid">8.2.2, 8.1.7, 8.0.11</td>
<td class="colMid">core server</td>
<td class="colMid">C</td>
+
<td class="colLast">A vulnerability involving changing the data type of a table column can easily be exploited to cause a backend crash, and in principle might be used to read database content that the user should not be able to access.</td>
</tr>
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-0555">CVE-2007-0555</a></td>
<td class="colMid">8.2, 8.1, 8.0, 7.4, 7.3</td>
<td class="colMid">8.2.2, 8.1.7, 8.0.11, 7.4.16, 7.3.13</td>
+
<td class="colMid">core server</td>
<td class="colMid">C</td>
<td class="colLast">A vulnerability allows suppressing the normal checks that a SQL function returns the data type it's declared to do. These errors can easily be exploited to cause a backend crash, and in principle might be used to read database content that the user should not be able to access.</td>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5542">CVE-2006-5542</a><br/><a href="http://www.postgresql.org/about/news.664">Announcement</a></td>
+
<td class="colMid">8.1</td>
<td class="colMid">8.1.5</td>
<td class="colMid">core server</td>
<td class="colMid">8.1.5, 8.0.9, 7.4.14</td>
<td class="colMid">core server</td>
<td class="colMid">D</td>
+
<td class="colLast">A bug in the coercion of unknown literals to ANYARRAY can cause a denial of service. A valid login is required to exploit this vulnerability.</td>
</tr>
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5540">CVE-2006-5540</a><br/><a href="http://www.postgresql.org/about/news.664">Announcement</a></td>
<td class="colMid">8.1</td>
<td class="colMid">8.1.5</td>
+
<td class="colMid">core server</td>
<td class="colMid">D</td>
<td class="colLast">A bug in the handling of aggregates in UPDATE can cause a denial of service. A valid login is required to exploit this vulnerability.</td>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2314">CVE-2006-2314</a><br/><a href="/docs/techdocs.52">FAQ</a></td>
+
<td class="colMid">8.1, 8.0, 7.4, 7.3</td>
<td class="colMid">8.1.4, 8.0.8, 7.4.13, 7.3.15</td>
<td class="colMid">core server</td>
<td class="colMid">8.1.4, 8.0.8, 7.4.13, 7.3.15</td>
<td class="colMid">core server</td>
<td class="colMid">A</td>
+
<td class="colLast">An attacker able to submit crafted strings to an application that will embed those strings in SQL commands can use invalidly-encoded multibyte characters to bypass standard string-escaping methods, resulting in possible SQL injection.</td>
</tr>
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0553">CVE-2006-0553</a><br/><a href="http://archives.postgresql.org/pgsql-announce/2006-02/msg00008.php">Announcement</a></td>
<td class="colMid">8.1</td>
<td class="colMid">8.1.3</td>
+
<td class="colMid">core server</td>
<td class="colMid">C</td>
<td class="colLast">A bug in the handling of SET ROLE allows escalation of privileges to any other database user, including superuser. A valid login is required to exploit this vulnerability.</td>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-0678">CVE-2006-0678</a><br/><a href="http://archives.postgresql.org/pgsql-announce/2006-02/msg00008.php">Announcement</a></td>
+
<td class="colMid">8.0, 7.4, 7.3</td>
<td class="colMid">8.0.7, 7.4.12, 7.3.14</td>
<td class="colMid">core server</td>
<td class="colMid">8.1.2, 8.0.6</td>
<td class="colMid">core server, win32 only</td>
<td class="colMid">B</td>
+
<td class="colLast">On Windows only, the postmaster will exit if too many connection requests arrive simultaneously. This does not affect existing database connections, but will prevent new connections from being established until the postmaster is manually restarted.</td>
</tr>
<td class="colFirst"><a href="http://archives.postgresql.org/pgsql-announce/2006-01/msg00001.php">Announcement</a></td>
<td class="colMid">8.1, 8.0, 7.4, 7.3</td>
<td class="colMid">8.1.2, 8.0.6, 7.4.11, 7.3.13</td>
+
<td class="colMid">contrib module</td>
<td class="colMid"></td>
<td class="colLast">There is a signedness bug in Openwall gen_salt code that pgcrypto uses. This makes the salt space for md5 and xdes algorithms a lot smaller than it should be. This only affects the gen_salt() function with md5 or xdes.</td>
<tr valign="top">
<td class="colFirst"><a href="http://www.postgresql.org/docs/8.0/static/release-8-0-3.html">Release notes</a></td>
<td class="colMid">8.0, 7.4</td>
+
<td class="colMid">8.0.3, 7.4.8</td>
<td class="colMid">core server</td>
<td class="colMid">D</td>
</tr>
<tr valign="top">
+
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-1410">CVE-2005-1410</a><br/><a href="http://archives.postgresql.org/pgsql-announce/2005-05/msg00001.php">Announcement</a></td>
<td class="colMid">8.0, 7.4</td>
<td class="colMid">8.0.3, 7.4.8</td>
<td class="colMid">contrib module</td>
<td class="colMid">D</td>
<td class="colLast">The tsearch2 contrib module declares several functions as internal even though they don't take an internal argument. This allows attackers to cause a denial of service and may possibly have other impacts. A valid login is required to exploit this vulnerability.<br/>Note! See the <a href="http://archives.postgresql.org/pgsql-announce/2005-05/msg00001.php">announcement</a> for special upgrade instructions.</td>
+
</tr>
<tr valign="top">
<td class="colMid">8.0, 7.4, 7.3</td>
<td class="colMid">8.0.3, 7.4.8, 7.3.10</td>
<td class="colMid">core server</td>
+
<td class="colMid">D</td>
<td class="colLast">Public EXECUTE access is given to certain character conversion functions that are not designed to be safe against malicious arguments. This can cause at least a denial of service. A valid login is required to exploit this vulnerability.<br/>Note! See the <a href="http://archives.postgresql.org/pgsql-announce/2005-05/msg00001.php">announcement</a> for special upgrade instructions.</td>
</tr>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0247">CVE-2005-0247</a></td>
+
<td class="colMid">8.0, 7.4</td>
<td class="colMid">8.0.2, 7.4.8</td>
<td class="colMid">core server</td>
<td class="colMid">8.0.1, 7.4.7, 7.3.9</td>
<td class="colMid">contrib module</td>
<td class="colMid">D</td>
+
<td class="colLast">The intagg contrib module allows attackers to cause a denial of service. A valid login is required to exploit this vulnerability.</td>
</tr>
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0245">CVE-2005-0245</a></td>
<td class="colMid">8.0, 7.4, 7.3</td>
<td class="colMid">8.0.1, 7.4.7, 7.3.10</td>
+
<td class="colMid">core server</td>
<td class="colMid">C</td>
<td class="colLast">Multiple buffer overflows in the PL/PGSQL parser may allow attackers to execute arbitrary code. A valid login is required to exploit this vulnerability.</td>
<tr valign="top">
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0244">CVE-2005-0244</a></td>
+
<td class="colMid">8.0, 7.4, 7.3</td>
<td class="colMid">8.0.1, 7.4.7, 7.3.9</td>
<td class="colMid">core server</td>
<td class="colMid">8.0.1, 7.4.7, 7.3.9</td>
<td class="colMid">core server</td>
<td class="colMid">C</td>
+
<td class="colLast">Any database user is permitted to load arbitrary shared libraries using the LOAD command. A valid login is required to exploit this vulnerability.</td>
</tr>
<td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-0977">CVE-2005-0977</a></td>
<td class="colMid">7.4, 7.3</td>
<td class="colMid">7.4.6, 7.3.8</td>
+
<td class="colMid">client contrib module</td>
<td class="colMid"></td>
<td class="colLast">Contrib script make_oidjoins_check uses unsafe temporary files. This script is not a user-facing script.</td>
<tr valign="top">
<td class="colFirst"><a href="http://www.postgresql.org/docs/7.4/static/release-7-4-3.html">Release notes</a></td>
<td class="colMid">7.4</td>
+
<td class="colMid">7.4.3</td>
<td class="colMid">core server</td>
<td class="colMid">C</td>
<td class="colLast">A buffer overrun vulnerability exists in the enlargeStringInfo function and can be triggered by injecting bogus data in the datastream of an existing connection. A valid login is required to exploit this vulnerability.</td>
</tr>
-
- <tr valign="top">
- <td class="colFirst"><a href="http://www.postgresql.org/docs/7.3/static/release-7-3-6.html">Release notes</a></td>
- <td class="colMid">7.3</td>
- <td class="colMid">7.3.6</td>
- <td class="colMid">core server</td>
- <td class="colMid">C</td>
- <td class="colLast">A patch applied in 7.3.3 to fix a corner case in rule permissions checks turns out to have disabled rule-related permissions checks in many not-so-corner cases. This would for example allow users to insert into views they weren't supposed to have permission to insert into. A valid login is required to exploit this vulnerability.</td>
- </tr>
-
- <tr valign="top">
- <td class="colFirst"><a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0901">CVE-2003-0901</a></td>
- <td class="colMid">7.3</td>
- <td class="colMid">7.3.4</td>
- <td class="colMid">core server</td>
- <td class="colMid">C</td>
- <td class="colLast">A buffer overflow in the to_ascii function allows attackers to execute arbitrary code. A valid login is required to exploit this vulnerability.</td>
- </tr>
-
- <tr valign="top" class="lastrow">
- <td class="colFirst"><a href="http://www.postgresql.org/docs/7.3/static/release-7-3-2.html">Release notes</a></td>
- <td class="colMid">7.3</td>
- <td class="colMid">7.3.2</td>
- <td class="colMid">core server</td>
- <td class="colMid">C</td>
- <td class="colLast">The fastpath function interface did not properly check for permissions before executing a function. A valid login is required to exploit this vulnerability.</td>
- </tr>
</table>
</div>
-<a name="sec"></a>
-<h2>Severities</h2>
+<a name="cls"></a>
+<h2>Vulnerability Classes</h2>
<p>
-The following severity references are used in the above table:
+The following vulnerability class references are used in the above table:
</p>
<div class="tblBasic">
<table border="0" cellpadding="0" cellspacing="0" class="tblBasicGrey">
<tr>
- <th class="colFirst">Severity</th>
+ <th class="colFirst">Class</th>
<th class="colLast">Description</th>
+
</tr>
<tr valign="top">
<tr valign="top">
<td class="colFirst">C</td>
+
<td class="colLast">A vulnerabilty that is exploitable for privilege escalation, but requiring a valid prior login.</td>
</tr>
</tr>
</table>
+
</div>
<a name="comp"></a>
<table border="0" cellpadding="0" cellspacing="0" class="tblBasicGrey">
<tr>
<th class="colFirst">Component</th>
+
<th class="colLast">Description</th>
</tr>
<tr valign="top">
<td class="colFirst">contrib module</td>
<td class="colLast">This vulnerability exists in a contrib modules. Contrib modules are not installed by default when PostgreSQL is installed from source. They may be installed by binary packages.</td>
+
</tr>
<tr valign="top" class="lastrow">
</table>
</div>
+
{%endblock%}
projects / pgweb.git / commitdiff