First published: Mon Mar 02 2009(Updated: )
A stack overflow was found in how PostgreSQL handles conversion encoding. This could allow an authenticated user to kill connections to the PostgreSQL server for a small amount of time, which could interupt transactions by other users/clients. The original report is here: <a href="http://archives.postgresql.org/pgsql-bugs/2009-02/msg00172.php">http://archives.postgresql.org/pgsql-bugs/2009-02/msg00172.php</a> Upstream has a patch for this issue that causes the server to crash in a different way (core dump due to abort() rather than core dump due to stack overflow), but it sounds like they are still looking for a better fix.
Affected Software | Affected Version | How to fix |
---|---|---|
PostgreSQL JDBC Driver |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-488156 is classified as moderate due to the potential risk of connection interruption.
To fix REDHAT-BUG-488156, ensure you are using the latest stable version of PostgreSQL that addresses the stack overflow vulnerability.
Authenticated users of PostgreSQL are affected by REDHAT-BUG-488156 because it allows them to disrupt connections.
The impact of REDHAT-BUG-488156 is that it can cause temporary disruptions to transactions for users connected to the PostgreSQL server.
Yes, the PostgreSQL JDBC Driver is affected by REDHAT-BUG-488156 as it utilizes PostgreSQL's encoding conversion mechanisms.