|
Bugzilla – Full Text Bug Listing |
| Summary: | VUL-0: CVE-2004-0777: courier-imap: format string vulnerability | ||
|---|---|---|---|
| Product: | [Novell Products] SUSE Security Incidents | Reporter: | Ludwig Nussel <lnussel> |
| Component: | Incidents | Assignee: | Thorsten Kukuk <kukuk> |
| Status: | RESOLVED FIXED | QA Contact: | Security Team bot <security-team> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | security-team |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | CVE-2004-0777: CVSS v2 Base Score: 7.5 (AV:N/AC:L/Au:N/C:P/I:P/A:P) | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | patch to fix problem | ||
|
Description
Ludwig Nussel
2004-08-19 23:12:57 UTC
So the default is that debugging is disabled. This is the case for our versions. Do we really need to do something here for a leaf package? Well, according to a guy that answered the advisory it is not quite as harmless as is sounds. An attacker trying to exploit this would try to disturb the service first to have the admin turn on debugging to see what's going on. please check the versions mentioned in the advisory and in the release branches. Newer versions of courier-imap are not affected. We introduced it with 9.0 and only 9.0 is affected, since 9.1 has a newer one where the code looks more correct. Created attachment 22810 [details]
patch to fix problem
patch to fix.
compiles, but untested.
About comment #3: The advisory is not correct: They claim 2.x as defect and fixed with 3.0.7. But 3.0-3.0.6 are also defect (but they say nothing about this). Our 9.1 version has the same code as 9.0 in debug.c. The problem is: Did anybody of you ever run an online update on 9.0 with an old computer and modem? I hope you will not need your phone during the next days after starting it. We have to compare the risk of the defect with usability and the risk to update. And in this case, there is only a very low risk (if the admin forgets to disable debug mode after he used it), compared with a higher risk that something during the update goes wrong, a bad usability and the bad press that there are more updates than GB on CDs (people are complaining about this already, computer magazines are complaining about this and we try to create PatchCDs for them so that they are more happy). Applying this small patch to both versions is no problem, but it seems nobody thinks about the work and consequences which follows of this. About comment #2: This answer is stupid. If the admin switch on debugging to see what's going on, he will see the attackers try to compromise the service. And he will watch the log file because he enabled it do to so to fix the service. #3, yes, you are right. the same patch would apply. Regarding the need of an update ... I agree with your points. I think this issue is not important enough to warrant an update, but we must make sure it is fixed in STABLE. It was fixed in STABLE 4 days ago ;-) CVE-2004-0777: CVSS v2 Base Score: 7.5 (AV:N/AC:L/Au:N/C:P/I:P/A:P) |