Alstrasoft Epay Pro 2.0 and prior Directory Traversal Vulnerability

Risk: Medium
Local: No
Remote: Yes

CVSS Base Score: 5/10
Impact Subscore: 2.9/10
Exploitability Subscore: 10/10
Exploit range: Remote
Attack complexity: Low
Authentication: No required
Confidentiality impact: Partial
Integrity impact: None
Availability impact: None

------------------------------------------------------ HYA-2005-008 Advisory 008 ------------------------------------------------------ Date - Mon Sep 19 2005 TITLE: ====== Alstrasoft Epay Pro 2.0 and prior Directory Traversal Vulnerability SEVERITY: ========= Medium SOFTWARE: ========= Alstrasoft EPay Pro v2.0 and prior INFO: ===== EPay Pro is the ultimate software solution for those who wish to run their own Paypal, Stormpay, or e-gold type of online business. Epay Pro comes with a ready out of the box website with all the features you need to run your own payment gateway system. Support Website : BUG DESCRIPTION: ================ EPay Pro version 2.0 and prior are vulnerable caused by an improper validation of user-supplied input. A remote attacker could embed in the index.php etc/passwd containing embedded code in the payment or send parameter which, once the link is clicked, would be executed to see passwords within the security context of the hosting server. An attacker could use this vulnerability to see all the victim's password authentication credentials. POC: ==== Here is an example: http://targeturl/index.php?read=../../../../../../../../../../../../../. ./etc/passwd VENDOR STATUS: ============== Vendor has been contacted but no response recieved till date. FIX: ==== No fix available as of date. CREDITS: ======== This vulnerability was discovered and researched by GeMe-GeMeS of h4cky0u Security Forums. mail : GeMeGeMeS at Gmail.Com web : ORIGINAL ADVISORY: ==================

Vote for this issue:


Thanks for you vote!


Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2019,


Back to Top