|
Zoo "parse()" File Name Handling Buffer Overflow
|
|
Secunia Advisory:
|
SA19250
|
|
|
Release Date:
|
2006-03-16
|
|
Last Update:
|
2006-03-21
|
|
Popularity:
|
7,063 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Privilege escalation
|
|
Where:
|
Local system
|
|
Solution Status:
|
Unpatched
|
|
| Software: | zoo 2.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Josh Bressers has reported a vulnerability in zoo, which potentially can be exploited by malicious, local users to gain escalated privileges.
The vulnerability is caused due to a boundary error within the "parse()" function in parse.c when creating an archive from a file with an overly long pathname. This can be exploited to cause a stack-based buffer overflow and may allow arbitrary code execution.
Successful exploitation requires that the user is e.g. tricked into adding a file that is located in directories with overly long names into an archive.
The vulnerability has been reported in version 2.10. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
