PHP SNMPGet Function Local Buffer Overflow Vulnerability
BID:22893
Info
PHP SNMPGet Function Local Buffer Overflow Vulnerability
| Bugtraq ID: | 22893 |
| Class: | Boundary Condition Error |
| CVE: |
CVE-2007-1413 |
| Remote: | No |
| Local: | Yes |
| Published: | Mar 09 2007 12:00AM |
| Updated: | May 12 2015 07:29PM |
| Credit: | rgod is credited with the discovery of this vulnerability. |
| Vulnerable: |
PHP PHP 5.2.3 PHP PHP 5.2.2 PHP PHP 5.2.1 PHP PHP 4.4.6 PHP PHP 5.2 |
| Not Vulnerable: | |
Discussion
PHP SNMPGet Function Local Buffer Overflow Vulnerability
PHP is prone to a local buffer-overflow vulnerability because the application fails to perform boundary checks before copying user-supplied data to insufficiently sized memory buffers.
An attacker can exploit this issue to execute arbitrary machine code in the context of the affected webserver. Failed exploit attempts will likely crash the webserver, denying service to legitimate users.
PHP 4.4.6 for Microsoft Windows is vulnerable; other versions may also be affected.
PHP is prone to a local buffer-overflow vulnerability because the application fails to perform boundary checks before copying user-supplied data to insufficiently sized memory buffers.
An attacker can exploit this issue to execute arbitrary machine code in the context of the affected webserver. Failed exploit attempts will likely crash the webserver, denying service to legitimate users.
PHP 4.4.6 for Microsoft Windows is vulnerable; other versions may also be affected.
Exploit / POC
PHP SNMPGet Function Local Buffer Overflow Vulnerability
The following proofs of concept and exploits are available:
The following proofs of concept and exploits are available:
Solution / Fix
PHP SNMPGet Function Local Buffer Overflow Vulnerability
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].
Solution:
Currently we are not aware of any vendor-supplied patches for this issue. If you feel we are in error or if you are aware of more recent information, please mail us at: [email protected].