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

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the Oracle JInitiator ActiveX control, requiring user interaction to load the malicious page.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f4m6-pc47-p952

## What is CVE-2007-4467?

CVE-2007-4467 is a critical memory corruption vulnerability in n/a, published on 31 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple stack-based buffer overflows in the Oracle JInitiator ActiveX control (beans.ocx) 1.1.8.16 and earlier, as used by Oracle Forms applications from Oracle and third parties, allow remote attackers to execute arbitrary code via unspecified "initialization parameters." NOTE: it was later reported that 1.1.8.3 through 1.1.8.25, and probably 1.1.5.x and 1.1.7.x, are affected.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Oracle Jinitiator.

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

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

## Is CVE-2007-4467 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1823](https://insights.sbomify.com/CVE-2008-1823/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-4467 is a critical memory corruption vulnerability in n/a, published on 31 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-4467 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-4467/ (Markdown: https://insights.sbomify.com/CVE-2007-4467/index.md)
```

## Sources

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

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