Bug 155375
| Summary: | CAN-2005-0102 Integer overflow in camel-lock-helper | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Dave Malcolm <dmalcolm> |
| Component: | evolution | Assignee: | Dave Malcolm <dmalcolm> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | security-response-team |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | impact=low,source=vendorsec,reported=20050124,public=20050118 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-05-04 15:06:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 155503 | ||
built; will be part of RHSA-2005:397 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-397.html |
email from bressers: Message by NotZed: http://lists.ximian.com/archives/public/evolution-patches/2005-January/008672.html CVS commit: http://cvs.gnome.org/viewcvs/evolution/camel/camel-lock-helper.c?rev=1.7&hideattic=0&view=log We don't set the camel-lock-helper executable suid or sgid. I belive this is a non issue then. CAN-2005-0102 Dave said it's not suid/sgid for us and can't be affected by an email message -- however it's only not setuid because we don't build the srpms as root, if we did it would be - hence we need an update for this, but "low" severity impact=low,source=vendorsec,reported=20050124