# CVE-2010-4167: Path traversal in n/a

> Local attackers can gain privileges by placing a malicious configuration file in the current working directory when specific build options are enabled.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Nov 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2010-4167, GHSA-47hr-2rq3-9pw5, RHSA-2012:0301

## What is CVE-2010-4167?

CVE-2010-4167 is a medium-severity path traversal vulnerability in Imagemagick Imagemagick, published on 22 Nov 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Untrusted search path vulnerability in configure.c in ImageMagick before 6.6.5-5, when MAGICKCORE_INSTALLED_SUPPORT is defined, allows local users to gain privileges via a Trojan horse configuration file in the current working directory.

## Which versions are affected by CVE-2010-4167?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ImageMagick` | Red Hat:enterprise_linux:5::client | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-c++` | Red Hat:enterprise_linux:5::client | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-perl` | Red Hat:enterprise_linux:5::client | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-c++-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick` | Red Hat:enterprise_linux:5::server | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-c++` | Red Hat:enterprise_linux:5::server | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-c++-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:6.2.8.0-12.el5 |
| `ImageMagick-perl` | Red Hat:enterprise_linux:5::server | All versions | 0:6.2.8.0-12.el5 |

Products: Imagemagick Imagemagick.

## How do I fix CVE-2010-4167?

Upgrade to a fixed version.

## Is CVE-2010-4167 being exploited?

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

## Other vulnerabilities in Imagemagick Imagemagick

- [CVE-2019-19952](https://insights.sbomify.com/CVE-2019-19952/): Use after free in n/a (critical 9.8)
- [CVE-2018-16328](https://insights.sbomify.com/CVE-2018-16328/): Null dereference in n/a (critical 9.8)
- [CVE-2018-16329](https://insights.sbomify.com/CVE-2018-16329/): Null dereference in n/a (critical 9.8)
- [CVE-2017-18210](https://insights.sbomify.com/CVE-2017-18210/): Null dereference in n/a (critical 9.8)
- [CVE-2017-14138](https://insights.sbomify.com/CVE-2017-14138/): Denial of service in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-4167 and fix it if it is affected.

What it is: CVE-2010-4167 is a medium-severity path traversal vulnerability in Imagemagick Imagemagick, published on 22 Nov 2010. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-4167 in the wild and no public exploit code.

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

## Sources

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

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