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

> A memory corruption vulnerability in the PHP Ovrimos extension allows attackers to execute arbitrary code via an arbitrary address free operation.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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 stated
- **Fix available:** No
- **Published:** 10 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g6vw-7329-r3mc

## What is CVE-2007-1379?

CVE-2007-1379 is a medium-severity memory corruption vulnerability in Php Php, published on 10 Mar 2007. 

### Official description

The ovrimos_close function in the Ovrimos extension for PHP before 4.4.5 can trigger efree of an arbitrary address, which might allow context-dependent attackers to execute arbitrary code.

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

It affects 1 product.


Products: Php Php.

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

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

## Is CVE-2007-1379 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1379 is a medium-severity memory corruption vulnerability in Php Php, published on 10 Mar 2007. 
Exploitation: There is no known exploitation of CVE-2007-1379 in the wild and no public exploit code.

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

## Sources

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

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