CVE-2003-1432 Epic Games Unreal Engine 226f through 436 allows remote attackers to cause a denial of service (CPU consumption or crash) and possibly execu
Critical 10.0
Published
Updated
Check this codebase for CVE-2003-1432 and fix it if it is affected.
What it is: CVE-2003-1432 is a critical vulnerability in n/a, published on 23 Oct 2007.
Exploitation: There is no known exploitation of CVE-2003-1432 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-2003-1432/ (Markdown: https://insights.sbomify.com/CVE-2003-1432/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2003-1432?
CVE-2003-1432 is a critical vulnerability in n/a, published on 23 Oct 2007.
Official description
Epic Games Unreal Engine 226f through 436 allows remote attackers to cause a denial of service (CPU consumption or crash) and possibly execute arbitrary code via (1) a packet with a negative size value, which is treated as a large positive number during memory allocation, or (2) a negative size value in a package file.
Which versions are affected by CVE-2003-1432?
It affects 2 products.
Products include Epic Games Unreal Engine, Epic Games Unreal Tournament 2003.
How do I fix CVE-2003-1432?
No fix has been published for CVE-2003-1432 yet. Limit exposure of the affected software until one is available.
Is CVE-2003-1432 being exploited?
There is no known exploitation of CVE-2003-1432 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-h457-7gvf-jx74.