CVE-2007-1379: Medium severity PHP PHP vulnerability

Published Mar 10, 2007
·
Updated

The ovrimosclose function in the Ovrimos extension for PHP before 4.4.5 can trigger efree of an arbitrary address, which might allow context-dependent attackers to execute arbitrary code.

Affected Software

67 affected components
PHP PHP=4.3.9
PHP PHP=3.0
PHP PHP=4.0-beta1
PHP PHP=3.0.5
PHP PHP=3.0.11
PHP PHP=4.0-beta4
PHP PHP=4.2.0
PHP PHP=3.0.1
PHP PHP=3.0.2
PHP PHP=4.4.4
PHP PHP=4.1.0
PHP PHP=4.3.4
PHP PHP=4.0.4
PHP PHP=4.3.0
PHP PHP=4.0.5
PHP PHP=3.0.8
PHP PHP=4.3.6
PHP PHP=3.0.13
PHP PHP=4.0.7-rc2
PHP PHP=4.3.7
PHP PHP=4.0.7-rc1
PHP PHP=4.2.2
PHP PHP=4.4.2
PHP PHP=4.0-rc1
PHP PHP=3.0.7
PHP PHP=4.3.2
PHP PHP=4.3.11
PHP PHP=4.0.0
PHP PHP=3.0.6
PHP PHP=4.0.3-patch1
PHP PHP=3.0.17
PHP PHP=4.0.7
PHP PHP=4.0.2
PHP PHP=4.3.3
PHP PHP=4.1.1
PHP PHP=3.0.15
PHP PHP=3.0.16
PHP PHP=4.4.3
PHP PHP=3.0.10
PHP PHP=3.0.4
PHP PHP=4.2.3
PHP PHP=4.0.1-patch1
PHP PHP=4.0
PHP PHP=4.0-beta2
PHP PHP=4.0.1-patch2
PHP PHP=4.0.6
PHP PHP=4.1.2
PHP PHP=4.0.7-rc3
PHP PHP=4.0-rc2
PHP PHP=4.3.1
PHP PHP=3.0.18
PHP PHP=4.0-beta_4_patch1
PHP PHP=4.4.0
PHP PHP=4.3.10
PHP PHP=4.2.1
PHP PHP=4.0.4-patch1
PHP PHP=4.0.1
PHP PHP=3.0.12
PHP PHP=4.2
PHP PHP=4.4.1
PHP PHP=4.0-beta3
PHP PHP=4.0.3
PHP PHP=3.0.14
PHP PHP=3.0.9
PHP PHP=3.0.3
PHP PHP=4.3.8
PHP PHP=4.3.5

Event History

Mar 10, 2007
CVE Published
12:19 AM
CVE Published
via MITRE·05:00 AM
Data Sourced
via MITRE·05:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2007-1379?

CVE-2007-1379 has a high severity rating due to the potential for attackers to execute arbitrary code.

2

How do I fix CVE-2007-1379?

To fix CVE-2007-1379, upgrade to PHP version 4.4.5 or later which addresses the vulnerability.

3

Who is affected by CVE-2007-1379?

CVE-2007-1379 affects various versions of PHP prior to 4.4.5, including version 3.0 and earlier 4.x releases.

4

What types of attacks can CVE-2007-1379 enable?

CVE-2007-1379 can allow context-dependent attackers to execute arbitrary code, leading to potential system compromise.

5

Is there a workaround for CVE-2007-1379 while waiting for a patch?

No official workaround is recommended for CVE-2007-1379; the best course of action is to update PHP to a secure version.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203