CVE-2006-1017 in the critical feed json
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 funct…
published 2006-03-07 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1021
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- php7 openSUSE Tumbleweed 7.4.24-1.1
- php8 openSUSE Tumbleweed 8.0.11-1.1
opensuse advisories openSUSE-SU-2024:11167-1openSUSE-SU-2024:11169-1
Exploit prediction
3.10% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Technology feeds
References
-
mandriva.com
/security/advisories?name=MDKSA-2006:122
vendor-advisory
-
vupen.com
/english/advisories/2006/0772
vdb-entry, vendor-advisory
-
secunia.com
/advisories/21050
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/21546
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/18694
third-party-advisory, vendor-advisory
- php.net /release_5_1_5.php
-
osvdb.org
/23535
vdb-entry
-
securityreason.com
/securityalert/516
third-party-advisory
- bugs.php.net /bug.php?id=37265
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24964
vdb-entry
- php.net /ChangeLog-5.php#5.1.5
-
securityfocus.com
/archive/1/426339/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-1017
- NVD CVE-2006-1017
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.