CVE-2010-1447Not scoredCWE-264

CVE-2010-1447: Postgresql vulnerability

Postgresql

Vendor fix available · Affected: Postgresql · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.8%probability of exploitation in the next 30 days

86th percentile

050100

Higher than 86% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

The Safe (aka Safe.pm) module 2.26, and certain earlier versions, for Perl, as used in PostgreSQL 7.4 before 7.4.29, 8.0 before 8.0.25, 8.1 before 8.1.21, 8.2 before 8.2.17, 8.3 before 8.3.11, 8.4 before 8.4.4, and 9.0 Beta before 9.0 Beta 2, allows context-dependent attackers to bypass intended (1) Safe::reval and (2) Safe::rdo access restrictions, and inject and execute arbitrary code, via vectors involving subroutine references and delayed execution.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Permissions, Privileges, and Access Controls · Access Control
Vendor: Postgresql
Published: May 2010
Band: Possible (1 to 10%), May 2010

CoverageNo articles yet

No CyberSIXT article names CVE-2010-1447 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

8 more references are in the CVE record.