medium
5
CWE
20
Advisory Published
Updated

CVE-2006-7243: Input Validation

First published: Tue Jan 18 2011(Updated: )

PHP before 5.3.4 accepts the \0 character in a pathname, which might allow context-dependent attackers to bypass intended access restrictions by placing a safe file extension after this character, as demonstrated by .php\0.jpg at the end of the argument to the file_exists function.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
PHP=4.3.9
PHP=4.4.9
PHP=3.0
PHP=5.2.9
PHP=4.0-beta1
PHP=3.0.5
PHP=3.0.11
PHP=5.2.4
PHP=5.1.5
PHP=5.1.2
PHP=4.0-beta4
PHP=5.3.1
PHP=4.2.0
PHP=5.1.1
PHP=3.0.1
PHP=5.2.14
PHP=3.0.2
PHP=4.4.4
PHP=5.0.0-beta1
PHP=4.1.0
PHP=5.1.6
PHP=5.2.16
PHP=4.3.4
PHP=4.0.4
PHP=4.3.0
PHP=4.0.5
PHP=5.2.7
PHP=5.2.2
PHP=3.0.8
PHP=5.0.5
PHP=4.3.6
PHP=3.0.13
PHP=5.0.1
PHP=5.1.4
PHP=5.2.5
PHP=4.3.7
PHP=5.0.4
PHP=4.2.2
PHP=4.4.2
PHP=5.2.12
PHP=3.0.7
PHP=4.3.2
PHP=4.3.11
PHP=4.0.0
PHP=3.0.6
PHP=3.0.17
PHP=4.0.7
PHP=4.0.2
PHP=4.3.3
PHP<=5.3.3
PHP=2.0
PHP=4.1.1
PHP=3.0.15
PHP=3.0.16
PHP=5.2.11
PHP=5.2.6
PHP=5.2.17
PHP=5.3.0
PHP=4.4.3
PHP=5.0.0-rc2
PHP=5.2.3
PHP=5.0.3
PHP=3.0.10
PHP=3.0.4
PHP=4.2.3
PHP=5.1.0
PHP=4.4.5
PHP=5.2.13
PHP=5.0.0-rc3
PHP=4.0
PHP=4.0-beta2
PHP=2.0b10
PHP=4.4.8
PHP=4.0.6
PHP=5.2.0
PHP=5.2.4
PHP=4.1.2
PHP=5.0.0-beta3
PHP=5.3.2
PHP=4.3.1
PHP=5.1.3
PHP=3.0.18
PHP=4.0-beta_4_patch1
PHP=4.4.0
PHP=5.2.10
PHP=4.3.10
PHP=4.2.1
PHP=5.0.0-rc1
PHP=4.0.1
PHP=1.0
PHP=5.0.2
PHP=4.4.6
PHP=3.0.12
PHP=5.2.15
PHP=4.4.1
PHP=4.0-beta3
PHP=5.2.1
PHP=4.0.3
PHP=3.0.14
PHP=3.0.9
PHP=3.0.3
PHP=5.0.0-beta4
PHP=5.0.0
PHP=4.3.8
PHP=4.3.5
PHP=5.0.0-beta2
PHP=5.2.8
PHP=4.4.7

Remedy

http://bugs.php.net/39863

Remedy

http://openwall.com/lists/oss-security/2010/11/18/4

Remedy

http://openwall.com/lists/oss-security/2010/11/18/5

Remedy

http://openwall.com/lists/oss-security/2010/12/09/10

Remedy

http://openwall.com/lists/oss-security/2010/12/09/9

Remedy

http://svn.php.net/viewvc?view=revision&revision=305412

Remedy

http://svn.php.net/viewvc?view=revision&revision=305507

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2006-7243?

    The CVE-2006-7243 vulnerability is classified as having a medium severity level due to its ability to bypass access restrictions.

  • How do I fix CVE-2006-7243?

    To remediate CVE-2006-7243, it is recommended to upgrade PHP to version 5.3.4 or later to ensure the \0 character in pathnames is not accepted.

  • What systems are affected by CVE-2006-7243?

    CVE-2006-7243 affects multiple versions of PHP, including versions 3.0 up to 5.3.3.

  • What types of attacks can exploit CVE-2006-7243?

    CVE-2006-7243 can be exploited by attackers to bypass access restrictions using specially crafted file paths that include the \0 character.

  • Is CVE-2006-7243 a zero-day vulnerability?

    CVE-2006-7243 is not classified as a zero-day vulnerability since it was reported and documented several years ago.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203