CVE-2005-0247Not scoredCWE-119

CVE-2005-0247: 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.

3.5%probability of exploitation in the next 30 days

89th percentile

050100

Higher than 89% of scored CVEs

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

DescriptionCVE.org

Multiple buffer overflows in gram.y for PostgreSQL 8.0.1 and earlier may allow attackers to execute arbitrary code via (1) a large number of variables in a SQL statement being handled by the read_sql_construct function, (2) a large number of INTO variables in a SELECT statement being handled by the make_select_stmt function, (3) a large number of arbitrary variables in a SELECT statement being handled by the make_select_stmt function, and (4) a large number of INTO variables in a FETCH statement being handled by the make_fetch_stmt function, a different set of vulnerabilities than CVE-2005-0245.

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: Memory Buffer Bounds · Memory Corruption
Vendor: Postgresql
Published: February 2005
Band: Possible (1 to 10%), February 2005

CoverageNo articles yet

No CyberSIXT article names CVE-2005-0247 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

3 more references are in the CVE record.