PostgreSQL up to 7.4.7 contrib/intagg code injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k0.00

Summaryinfo

A vulnerability was found in PostgreSQL up to 7.4.7. It has been declared as problematic. This affects the function contrib/intagg. Executing a manipulation can lead to code injection. This vulnerability appears as CVE-2005-0227. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in PostgreSQL up to 7.4.7 (Database Software). It has been declared as critical. This vulnerability affects the function contrib/intagg. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

PostgreSQL (pgsql) 7.4.x, 7.2.x, and other versions allows local users to load arbitrary shared libraries and execute code via the LOAD extension.

The bug was discovered 02/01/2005. The weakness was presented 02/01/2005 by Marc G. Fournier with postgresql.org (Website). The advisory is shared for download at archives.postgresql.org. This vulnerability was named CVE-2005-0227 since 02/05/2005. The attack can be initiated remotely. Required for exploitation is a single authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.

The vulnerability scanner Nessus provides a plugin with the ID 17129 (RHEL 2.1 : postgresql (RHSA-2005:150)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Red Hat Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19146 (PostgreSQL LOAD Extension Local Privilege Escalation Vulnerability).

Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at wwwmaster.postgresql.org. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published 3 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (17129), SecurityFocus (BID 12411†), OSVDB (13354†), Secunia (SA12948†) and Vulnerability Center (SBV-7856†). See VDB-1166, VDB-1169, VDB-1167 and VDB-23909 for similar entries. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Code injection
CWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 17129
Nessus Name: RHEL 2.1 : postgresql (RHSA-2005:150)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 52194
OpenVAS Name: FreeBSD Ports: postgresql, postgresql-server, ja-postgresql
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: wwwmaster.postgresql.org

Timelineinfo

02/01/2005 🔍
02/01/2005 +0 days 🔍
02/01/2005 +0 days 🔍
02/01/2005 +0 days 🔍
02/04/2005 +3 days 🔍
02/05/2005 +1 days 🔍
02/16/2005 +11 days 🔍
02/16/2005 +0 days 🔍
05/02/2005 +75 days 🔍
07/05/2025 +7369 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: archives.postgresql.org
Researcher: Marc G. Fournier
Organization: postgresql.org
Status: Confirmed

CVE: CVE-2005-0227 (🔍)
GCVE (CVE): GCVE-0-2005-0227
GCVE (VulDB): GCVE-100-1168

OVAL: 🔍

SecurityFocus: 12411 - PostgreSQL LOAD Extension Local Privilege Escalation Vulnerability
Secunia: 12948 - PostgreSQL Multiple Vulnerabilities, Less Critical
OSVDB: 13354 - CVE-2005-0227 - PostgreSQL - Code Execution Issue
Vulnerability Center: 7856

See also: 🔍

Entryinfo

Created: 02/04/2005 14:20
Updated: 07/05/2025 16:33
Changes: 02/04/2005 14:20 (82), 07/01/2019 09:15 (5), 06/29/2024 15:28 (17), 07/05/2025 16:33 (5)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!