# CVE-2006-1017: Security feature bypass in n/a

> Remote attackers can bypass safe_mode and open_basedir restrictions in PHP IMAP applications to access unauthorized IMAP data.

- **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:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8m3r-mrww-j5pv

## What is CVE-2006-1017?

CVE-2006-1017 is a critical vulnerability in Php Php, published on 7 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The c-client library 2000, 2001, or 2004 for PHP before 4.4.4 and 5.x before 5.1.5 do not check the (1) safe_mode or (2) open_basedir functions, and when used in applications that accept user-controlled input for the mailbox argument to the imap_open function, allow remote attackers to obtain access to an IMAP stream data structure and conduct unauthorized IMAP actions.

## Which versions are affected by CVE-2006-1017?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2006-1017?

Upgrade to a fixed version.

## Is CVE-2006-1017 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1017 and fix it if it is affected.

What it is: CVE-2006-1017 is a critical vulnerability in Php Php, published on 7 Mar 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1017 in the wild and no public exploit code.

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

## Sources

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

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