# CVE-2009-0663: Memory corruption in n/a

> Heap-based buffer overflow in Perl DBD::Pg module allows arbitrary code execution via crafted database row input.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-0663, GHSA-q57m-cgxh-vv5j

## What is CVE-2009-0663?

CVE-2009-0663 is a high-severity memory corruption vulnerability in n/a, published on 30 Apr 2009. 

### Official description

Heap-based buffer overflow in the DBD::Pg (aka DBD-Pg or libdbd-pg-perl) module 1.49 for Perl might allow context-dependent attackers to execute arbitrary code via unspecified input to an application that uses the getline and pg_getline functions to read database rows.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2009-0663?

It affects 1 product.


Products: Cmu Dbd\.

## How do I fix CVE-2009-0663?

Upgrade to a fixed version.

## Is CVE-2009-0663 being exploited?

There is no known exploitation of CVE-2009-0663 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0663 and fix it if it is affected.

What it is: CVE-2009-0663 is a high-severity memory corruption vulnerability in n/a, published on 30 Apr 2009. 
Exploitation: There is no known exploitation of CVE-2009-0663 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-0663/ (Markdown: https://insights.sbomify.com/CVE-2009-0663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-0663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-0663
- OSV: https://osv.dev/vulnerability/CVE-2009-0663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-0663/
Summaries are generated and may contain mistakes; the official description above is the record.