|
Bugzilla – Full Text Bug Listing |
| Summary: | VUL-0: CVE-2005-0247: new postgresql problems | ||
|---|---|---|---|
| Product: | [Novell Products] SUSE Security Incidents | Reporter: | Marcus Meissner <meissner> |
| Component: | Incidents | Assignee: | Security Team bot <security-team> |
| Status: | RESOLVED FIXED | QA Contact: | Security Team bot <security-team> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | max, security-team |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | CVE-2005-0247: CVSS v2 Base Score: 6.5 (AV:N/AC:L/Au:S/C:P/I:P/A:P) CVSSv2:NVD:CVE-2005-0227:4.3:(AV:L/AC:L/Au:S/C:P/I:P/A:P) | ||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Marcus Meissner
2005-02-10 21:37:27 UTC
<!-- SBZ_reproduce --> n/a CAN-2005-0227 has been fixed with the latest round of PostgreSQL patches already. any update? CAN-2005-0244, CAN-2005-0245, and CAN-2005-0246 have also already been fixed with the latest round of patch releases. The only exception is CAN-2005-0244, for which no fix shows up in PostgreSQL 7.2.7 (SLES8). I'll ask the PostgreSQL folks whether that version wasn't vulnerable or the fix was forgotten in the last patch release. So the only remaining issue we have to fix for all our products is CAN-2005-0247. CAN-2005-0244 was not relevant for 7.2.7. Fixes to CAN-2005-0247 for sles8, 9.0, sles9 and 9.2 have just been submitted. Sorry for the delay. what about 8.2? SM-Tracker-851 Is any subpackage besides postgresql-server affected at all? Oops, I forgot to submit 8.2. Will do it tomorrow. Only postgresql-server is affected by this patch, but of course the other subpackages from the recent version-update need to stay on the server. What about not automatically restarting the server in %post so we can remove the annoying popup? *grmbl* it's always postun of the old package so that's not possible. This is already being done, at least in the more recent versions, but it only works when the running server doesn't have any client connections. The other way would be to restart the server in a way so that it kills all current client connections, but I don't want to do that. That's why we have and need this popup. patchinfos submitted, I've included more info about CAN numbers. updates approved. needs advisory i think advisory released CVE-2005-0247: CVSS v2 Base Score: 6.5 (AV:N/AC:L/Au:S/C:P/I:P/A:P) |