# CVE-2007-5929: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code or crash the daemon via a buffer overflow in stored procedure names.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-679r-286m-46jm

## What is CVE-2007-5929?

CVE-2007-5929 is a critical memory corruption vulnerability in n/a, published on 10 Nov 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in OpenBase 10.0.5 and earlier might allow remote authenticated users to execute arbitrary code or cause a denial of service (daemon crash) by creating a stored procedure with a long name and invoking this procedure, which triggers heap corruption.

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

## Which versions are affected by CVE-2007-5929?

It affects 1 product.


Products: Openbase International Ltd Openbase.

## How do I fix CVE-2007-5929?

No fix has been published for CVE-2007-5929 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-5929 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-5926](https://insights.sbomify.com/CVE-2007-5926/): Command injection in n/a (critical 9.0)
- [CVE-2007-5927](https://insights.sbomify.com/CVE-2007-5927/): Path traversal in n/a (high 8.1)
- [CVE-2007-5928](https://insights.sbomify.com/CVE-2007-5928/): Memory corruption in n/a (high 8.1)
- [CVE-2006-5852](https://insights.sbomify.com/CVE-2006-5852/): Path traversal in n/a (medium 4.6)
- [CVE-2006-5851](https://insights.sbomify.com/CVE-2006-5851/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5929 and fix it if it is affected.

What it is: CVE-2007-5929 is a critical memory corruption vulnerability in n/a, published on 10 Nov 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-5929 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-2007-5929/ (Markdown: https://insights.sbomify.com/CVE-2007-5929/index.md)
```

## Sources

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

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