Menu

Star on GitHub · 3.2k

CVE-2010-3433

6.0 · MEDIUM

The PL/perl and PL/Tcl implementations in PostgreSQL 7.4 before 7.4.30, 8.0 before 8.0.26, 8.1 before 8.1.22, 8.2 before 8.2.18, 8.3 before 8.3.12, 8.4 before 8.4.5, and 9.0 before 9.0.1 do not pro…

Published Oct 6, 2010postgresqlCWE-264EPSS 3.33%

Overview

CVE-2010-3433 is a medium-severity vulnerability affecting postgresql postgresql. It was published on October 6, 2010 and has a CVSS 2.0 base score of 6.0 (MEDIUM).

This vulnerability has a CVSS 2.0 base score of 6.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

Technical description

The PL/perl and PL/Tcl implementations in PostgreSQL 7.4 before 7.4.30, 8.0 before 8.0.26, 8.1 before 8.1.22, 8.2 before 8.2.18, 8.3 before 8.3.12, 8.4 before 8.4.5, and 9.0 before 9.0.1 do not properly protect script execution by a different SQL user identity within the same session, which allows remote authenticated users to gain privileges via crafted script code in a SECURITY DEFINER function, as demonstrated by (1) redefining standard functions or (2) redefining operators, a different vulnerability than CVE-2010-1168, CVE-2010-1169, CVE-2010-1170, and CVE-2010-1447.

Remediation

Check the references section for vendor advisories and patches from postgresql. Update postgresql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2010-3433?

CVE-2010-3433 is a medium-severity vulnerability affecting postgresql postgresql. It was published on October 6, 2010 and has a CVSS 2.0 base score of 6.0 (MEDIUM).

How severe is CVE-2010-3433?

This vulnerability has a CVSS 2.0 base score of 6.0, rated MEDIUM. It can be exploited remotely over the network. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2010-3433?

Check the references section for vendor advisories and patches from postgresql. Update postgresql to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2010-3433?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2010-3433 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2010

View all