This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 449337 - Bring various components of Satellite Server 4.2 up to date
Bring various components of Satellite Server 4.2 up to date
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
:
Depends On:
Blocks: CVE-2007-6306 CVE-2004-0687 CVE-2004-0688 CVE-2004-0914 CVE-2005-3964 CVE-2005-0605 CVE-2004-0885 CVE-2006-7197 CVE-2005-2090 CVE-2007-0450 CVE-2006-3835 CVE-2005-3510 CVE-2007-1860 CVE-2005-4838 CVE-2007-2435 CVE-2007-1349 CVE-2007-1358 CVE-2007-2449 CVE-2007-2450 CVE-2007-3304 CVE-2006-5752 CVE-2007-3382 CVE-2007-3385 CVE-2007-2788 CVE-2007-2789 CVE-2007-1355 CVE-2007-4465 CVE-2007-0243 CVE-2007-5461 CVE-2007-5000 CVE-2007-6388 CVE-2006-1329 CVE-2008-0128 CVE-2006-0898 CVE-2006-0254
  Show dependency treegraph
 
Reported: 2008-06-02 05:29 EDT by Mark J. Cox (Product Security)
Modified: 2012-02-23 02:20 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-23 02:20:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Mark J. Cox (Product Security) 2008-06-02 05:29:49 EDT
Red Hat Network Satellite Server contains a number of components that since
release have been updated upstream to address security issues.  Red Hat Network
Satellite Server 4.2.3 contains updated versions and backported patches to these
components.

Although the CVE name list is long, these issues are not vulnerabilities that
would affect users of the Red Hat Network Satellite Server product in the normal
use of the product.
Comment 1 David Jorm 2012-02-23 02:20:33 EST
Satellite Server 4.2 is no longer supported.

Note You need to log in before you can comment on or make changes to this bug.