|
Bugzilla – Full Text Bug Listing |
| Summary: | VUL-0: CVE-2005-2349: directory traversal bug in zoo | ||
|---|---|---|---|
| Product: | [Novell Products] SUSE Security Incidents | Reporter: | Ludwig Nussel <lnussel> |
| Component: | Incidents | Assignee: | Security Team bot <security-team> |
| Status: | RESOLVED FIXED | QA Contact: | Security Team bot <security-team> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | atoptsoglou, security-team |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | archive that creates /etc/foo when extraced with zoo x | ||
|
Description
Ludwig Nussel
2004-10-14 20:09:40 UTC
Created attachment 24998 [details]
archive that creates /etc/foo when extraced with zoo x
the intention is to create directories only under the current working direcory, right? Yes. I think it is sufficient to fix it in STABLE. amavisd seems to extract each file to stdout individually and is therefore not affected. will fix for 9.3 did you fix it? fixes submitted Where does the patch come from, did you write it yourself? If so did you coordinate with upstream? Is the string you sanitize a directory or a file name? If it's a dir name it would probably still allow one level dir traversals if the path ends in ".." instead of "../". The patch is taken from Debian. It sanitizes a dirname. Could you please create an exploit with the few "../" and ".." on the end? The archive with the /etc/foo can be modified to contain the ".." on the end siply by swapping the "etc" and "..", but while not perfectly handled this is not an exploint, it can't leave the current directory. Striping the "etc" completely probably requires changing the CRC and I don't know how to do that. I have no idea how to create crafted zoo archives. Too uncritical to waste much time. We'll just accept the patch then. ok, fix submited with the check for ".." Secteam, how about writing some patchinfos? this was supposed to go into STABLE only. sorry for the confusion, fixed removed submissions for !STABLE |