What is the severity of CVE-2007-3007?

CVE-2007-3007 is considered a medium severity vulnerability due to its potential to expose sensitive file existence information.

How do I fix CVE-2007-3007?

To fix CVE-2007-3007, upgrade PHP to version 5.2.3 or later to ensure proper enforcement of open_basedir and safe_mode restrictions.

Which versions of PHP are affected by CVE-2007-3007?

CVE-2007-3007 affects PHP versions prior to 5.2.3, specifically those in the 5.0.0 to 5.2.2 range.

What attacks are possible with CVE-2007-3007?

CVE-2007-3007 may allow attackers to determine the existence of arbitrary files on the server, potentially leading to further exploitation.

Is CVE-2007-3007 still a concern today?

While CVE-2007-3007 is outdated, it may still be a concern for systems running unsupported versions of PHP.

Vulnerability/
CVE-2007-3007

medium

CWE

264

4/6/2007

7/8/2024

CVE-2007-3007

First published: Mon Jun 04 2007(Updated: )

PHP 5 before 5.2.3 does not enforce the open_basedir or safe_mode restriction in certain cases, which allows context-dependent attackers to determine the existence of arbitrary files by checking if the readfile function returns a string. NOTE: this issue might also involve the realpath function.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
PHP	>=5.0.0<5.2.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-3007?
CVE-2007-3007 is considered a medium severity vulnerability due to its potential to expose sensitive file existence information.
How do I fix CVE-2007-3007?
To fix CVE-2007-3007, upgrade PHP to version 5.2.3 or later to ensure proper enforcement of open_basedir and safe_mode restrictions.
Which versions of PHP are affected by CVE-2007-3007?
CVE-2007-3007 affects PHP versions prior to 5.2.3, specifically those in the 5.0.0 to 5.2.2 range.
What attacks are possible with CVE-2007-3007?
CVE-2007-3007 may allow attackers to determine the existence of arbitrary files on the server, potentially leading to further exploitation.
Is CVE-2007-3007 still a concern today?
While CVE-2007-3007 is outdated, it may still be a concern for systems running unsupported versions of PHP.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/weakness
agent/last-modified-date
agent/author
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
vendor/php
canonical/php
version/php/5.0.0

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.

Frequently Asked Questions

What is the severity of CVE-2007-3007?
CVE-2007-3007 is considered a medium severity vulnerability due to its potential to expose sensitive file existence information.
How do I fix CVE-2007-3007?
To fix CVE-2007-3007, upgrade PHP to version 5.2.3 or later to ensure proper enforcement of open_basedir and safe_mode restrictions.
Which versions of PHP are affected by CVE-2007-3007?
CVE-2007-3007 affects PHP versions prior to 5.2.3, specifically those in the 5.0.0 to 5.2.2 range.
What attacks are possible with CVE-2007-3007?
CVE-2007-3007 may allow attackers to determine the existence of arbitrary files on the server, potentially leading to further exploitation.
Is CVE-2007-3007 still a concern today?
While CVE-2007-3007 is outdated, it may still be a concern for systems running unsupported versions of PHP.