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

> Attackers can gain privileges via an unspecified overflow condition in BEA WebLogic Platform and Server.

- **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 stated
- **Fix available:** No
- **Published:** 23 Jan 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-448h-5p2g-9vwj

## What is CVE-2007-0425?

CVE-2007-0425 is a high-severity memory corruption vulnerability in Bea Weblogic Server, published on 23 Jan 2007. 

### Official description

Unspecified vulnerability in BEA WebLogic Platform and Server 8.1 through 8.1 SP5, and JRockit 1.4.2 R4.5 and earlier, allows attackers to gain privileges via unspecified vectors, related to an "overflow condition," probably a buffer overflow.

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

It affects 2 products.


Products: Bea Jrockit, Bea Weblogic Server.

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

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

## Is CVE-2007-0425 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0425 is a high-severity memory corruption vulnerability in Bea Weblogic Server, published on 23 Jan 2007. 
Exploitation: There is no known exploitation of CVE-2007-0425 in the wild and no public exploit code.

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

## Sources

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

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