|
Vulnerability Report: PostgreSQL 8.x
|
This vulnerability report for PostgreSQL 8.x contains a complete overview of all Secunia advisories affecting it. You can use this vulnerability report to ensure that you are aware of all vulnerabilities, both patched and unpatched, affecting this product allowing you to take the necessary precautions.
If you have information about a new or an existing vulnerability in PostgreSQL 8.x then you are more than welcome to contact us.
|
|
|
|
|
Vendor, Links, and Unpatched Vulnerabilities
| Vendor |
Postgresql
|
|
|
Product Link
|
View Here (Link to external site)
|
|
|
Affected By
|
12 Secunia advisories
31 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
0% (0 of 12 Secunia advisories)
|
|
Most Critical Unpatched
There are no unpatched Secunia advisories affecting this product, when all vendor patches are applied..
|
|
|
|
|
|
12 Secunia Advisories in 2003-2009
|
Secunia has issued a total of 12 Secunia advisories in 2003-2009 for PostgreSQL 8.x. Currently, 0% (0 out of 12) are marked as unpatched.
More information about the specific Secunia advisories affecting PostgreSQL 8.x can be found below. Each Secunia advisory is enclosed by a box highlighted with a color representing its current patch status. You can read the complete Secunia advisories for thorough descriptions of the issues covered and for solution suggestions by clicking either the Secunia advisory title or the "Read More" links available for each Secunia advisory.
|
|
|
|
|
|
Release Date: 2009-12-15 |
Secunia Advisory ID: SA37663 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Spoofing Privilege escalation
|
Where: From remote |
|
Short Description: Two vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to gain escalated privileges and by malicious people to conduct spoofing attacks. [Read More]
|
|
|
|
|
|
Release Date: 2009-09-10 |
Secunia Advisory ID: SA36660 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Security Bypass Privilege escalation DoS
|
Where: From local network |
|
Short Description: Some vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to gain escalated privileges and cause a DoS (Denial of Service), and by malicious people to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date: 2009-03-10 |
Secunia Advisory ID: SA34206 |
Solution Status: Partial Fix |
|
Criticality:
 |
Impact: Exposure of sensitive information DoS
|
Where: From local network |
|
Short Description: A weakness and a security issue have been reported in PostgreSQL, which can be exploited by malicious users to disclose potentially sensitive information or cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2008-01-07 |
Secunia Advisory ID: SA28359 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Privilege escalation DoS
|
Where: From local network |
|
Short Description: Some vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to gain escalated privileges or to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2007-04-24 |
Secunia Advisory ID: SA25019 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Privilege escalation
|
Where: From local network |
|
Short Description: A security issue has been reported in PostgreSQL, which potentially can be exploited by malicious users to gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2007-02-05 |
Secunia Advisory ID: SA24033 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Exposure of sensitive information DoS
|
Where: From local network |
|
Short Description: Some vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to gain knowledge of potentially sensitive information and cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2006-10-25 |
Secunia Advisory ID: SA22562 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: DoS
|
Where: From local network |
|
Short Description: Some vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2006-05-24 |
Secunia Advisory ID: SA20231 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Manipulation of data
|
Where: From remote |
|
Short Description: Two vulnerabilities have been reported in PostgreSQL, which potentially can be exploited by malicious people to conduct SQL injection attacks. [Read More]
|
|
|
|
|
|
Release Date: 2006-02-15 |
Secunia Advisory ID: SA18890 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Privilege escalation DoS
|
Where: From local network |
|
Short Description: Two vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to cause a DoS (Denial of Service) or gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2006-01-12 |
Secunia Advisory ID: SA18419 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Security Bypass DoS
|
Where: From local network |
|
Short Description: A vulnerability and a weakness has been reported in PostgreSQL, which potentially can be exploited by malicious, local users to bypass certain security restrictions and by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date: 2005-05-04 |
Secunia Advisory ID: SA15217 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Unknown Privilege escalation DoS
|
Where: From local network |
|
Short Description: Two vulnerabilities have been reported in PostgreSQL, which can be exploited by malicious users to cause a DoS (Denial of Service) or potentially gain escalated privileges. [Read More]
|
|
|
|
|
|
Release Date: 2005-02-01 |
Secunia Advisory ID: SA12948 |
Solution Status: Vendor Patch |
|
Criticality:
 |
Impact: Unknown Security Bypass Privilege escalation DoS
|
Where: From remote |
|
Short Description: Various vulnerabilities have been reported in PostgreSQL. Some have an unknown impact and others can can be exploited by malicious users to cause a DoS (Denial of Service), bypass certain security restrictions, or gain escalated privileges. [Read More]
|
|
|