# CVE-2014-2669: Integer overflow in n/a

> Remote authenticated users can trigger integer overflows in PostgreSQL hstore functions, potentially leading to code execution or denial of service.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mjx6-524j-mf72, UBUNTU-CVE-2014-2669

## What is CVE-2014-2669?

CVE-2014-2669 is a medium-severity vulnerability in Postgresql Postgresql, published on 28 Mar 2014. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple integer overflows in contrib/hstore/hstore_io.c in PostgreSQL 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users to have unspecified impact via vectors related to the (1) hstore_recv, (2) hstore_from_arrays, and (3) hstore_from_array functions in contrib/hstore/hstore_io.c; and the (4) hstoreArrayToPairs function in contrib/hstore/hstore_op.c, which triggers a buffer overflow.  NOTE: this issue was SPLIT from CVE-2014-0064 because it has a different set of affected versions.

Weakness: CWE-189

## Which versions are affected by CVE-2014-2669?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2014-2669?

Upgrade to a fixed version.

## Is CVE-2014-2669 being exploited?

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

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2669 and fix it if it is affected.

What it is: CVE-2014-2669 is a medium-severity vulnerability in Postgresql Postgresql, published on 28 Mar 2014. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-2669 in the wild and no public exploit code.

Affected product: Postgresql Postgresql. 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-2014-2669/ (Markdown: https://insights.sbomify.com/CVE-2014-2669/index.md)
```

## Sources

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

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