# CVE-2005-4344: Adobe (formerly Macromedia) ColdFusion MX 7.0 does not honor when the CFOBJECT /CreateObject(Java) setting is disabled, which allows local u


- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4c78-fmvp-hwrw

## What is CVE-2005-4344?

CVE-2005-4344 is a low-severity vulnerability in n/a, published on 17 Dec 2005. 

### Official description

Adobe (formerly Macromedia) ColdFusion MX 7.0 does not honor when the CFOBJECT /CreateObject(Java) setting is disabled, which allows local users to create an object despite the specified configuration.

## Which versions are affected by CVE-2005-4344?

It affects 1 product.


Products: Macromedia Coldfusion.

## How do I fix CVE-2005-4344?

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

## Is CVE-2005-4344 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1514](https://insights.sbomify.com/CVE-2001-1514/): Privilege escalation in n/a (critical 10.0)
- [CVE-2004-0646](https://insights.sbomify.com/CVE-2004-0646/): Memory corruption in n/a (critical 10.0)
- [CVE-2005-4342](https://insights.sbomify.com/CVE-2005-4342/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-1427](https://insights.sbomify.com/CVE-2001-1427/): File upload in n/a (high 7.5)
- [CVE-2002-1309](https://insights.sbomify.com/CVE-2002-1309/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4344 and fix it if it is affected.

What it is: CVE-2005-4344 is a low-severity vulnerability in n/a, published on 17 Dec 2005. 
Exploitation: There is no known exploitation of CVE-2005-4344 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-2005-4344/ (Markdown: https://insights.sbomify.com/CVE-2005-4344/index.md)
```

## Sources

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

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