Vulnerabilities > CVE-2007-5496 - Cross-Site Scripting vulnerability in Selinux Setroubleshoot 2.0.5

047910
CVSS 1.9 - LOW
Attack vector
LOCAL
Attack complexity
MEDIUM
Privileges required
NONE
Confidentiality impact
NONE
Integrity impact
PARTIAL
Availability impact
NONE

Summary

Cross-site scripting (XSS) vulnerability in setroubleshoot 2.0.5 allows local users to inject arbitrary web script or HTML via a crafted (1) file or (2) process name, which triggers an Access Vector Cache (AVC) log entry in a log file used during composition of HTML documents for sealert.

Vulnerable Configurations

Part Description Count
OS
Redhat
2
Application
Selinux
1

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Cross Site Scripting through Log Files
    An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
  • Embedding Scripts in Non-Script Elements
    This attack is a form of Cross-Site Scripting (XSS) where malicious scripts are embedded in elements that are not expected to host scripts such as image tags (<img>), comments in XML documents (< !-CDATA->), etc. These tags may not be subject to the same input validation, output validation, and other content filtering and checking routines, so this can create an opportunity for an attacker to tunnel through the application's elements and launch a XSS attack through other elements. As with all remote attacks, it is important to differentiate the ability to launch an attack (such as probing an internal network for unpatched servers) and the ability of the remote attacker to collect and interpret the output of said attack.
  • Embedding Scripts within Scripts
    An attack of this type exploits a programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. The attacker leverages this capability to execute scripts to execute his/her own script by embedding it within other scripts that the target software is likely to execute. The attacker must have the ability to inject script into script that is likely to be executed. If this is done, then the attacker can potentially launch a variety of probes and attacks against the web server's local environment, in many cases the so-called DMZ, back end resources the web server can communicate with, and other hosts. With the proliferation of intermediaries, such as Web App Firewalls, network devices, and even printers having JVMs and Web servers, there are many locales where an attacker can inject malicious scripts. Since this attack pattern defines scripts within scripts, there are likely privileges to execute said attack on the host. Of course, these attacks are not solely limited to the server side, client side scripts like Ajax and client side JavaScript can contain malicious scripts as well. In general all that is required is for there to be sufficient privileges to execute a script, but not protected against writing.
  • Cross-Site Scripting in Error Pages
    An attacker distributes a link (or possibly some other query structure) with a request to a third party web server that is malformed and also contains a block of exploit code in order to have the exploit become live code in the resulting error page. When the third party web server receives the crafted request and notes the error it then creates an error message that echoes the malformed message, including the exploit. Doing this converts the exploit portion of the message into to valid language elements that are executed by the viewing browser. When a victim executes the query provided by the attacker the infected error message error message is returned including the exploit code which then runs in the victim's browser. XSS can result in execution of code as well as data leakage (e.g. session cookies can be sent to the attacker). This type of attack is especially dangerous since the exploit appears to come from the third party web server, who the victim may trust and hence be more vulnerable to deception.
  • Cross-Site Scripting Using Alternate Syntax
    The attacker uses alternate forms of keywords or commands that result in the same action as the primary form but which may not be caught by filters. For example, many keywords are processed in a case insensitive manner. If the site's web filtering algorithm does not convert all tags into a consistent case before the comparison with forbidden keywords it is possible to bypass filters (e.g., incomplete black lists) by using an alternate case structure. For example, the "script" tag using the alternate forms of "Script" or "ScRiPt" may bypass filters where "script" is the only form tested. Other variants using different syntax representations are also possible as well as using pollution meta-characters or entities that are eventually ignored by the rendering engine. The attack can result in the execution of otherwise prohibited functionality.

Nessus

  • NASL familyScientific Linux Local Security Checks
    NASL idSL_20080521_SETROUBLESHOOT_ON_SL5_X.NASL
    descriptionA flaw was found in the way sealert wrote diagnostic messages to a temporary file. A local unprivileged user could perform a symbolic link attack, and cause arbitrary files, writable by other users, to be overwritten when a victim runs sealert. (CVE-2007-5495) A flaw was found in the way sealert displayed records from the setroubleshoot database as unescaped HTML. An local unprivileged attacker could cause AVC denial events with carefully crafted process or file names, injecting arbitrary HTML tags into the logs, which could be used as a scripting attack, or to confuse the user running sealert. (CVE-2007-5496) Additionally, the following bugs have been fixed in these update packages : - in certain situations, the sealert process used excessive CPU. These alerts are now capped at a maximum of 30, D-Bus is used instead of polling, threads causing excessive wake-up have been removed, and more robust exception-handling has been added. - different combinations of the sealert
    last seen2020-06-01
    modified2020-06-02
    plugin id60408
    published2012-08-01
    reporterThis script is Copyright (C) 2012-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/60408
    titleScientific Linux Security Update : setroubleshoot on SL5.x i386/x86_64
    code
    #%NASL_MIN_LEVEL 80502
    #
    # (C) Tenable Network Security, Inc.
    #
    # The descriptive text is (C) Scientific Linux.
    #
    
    include("compat.inc");
    
    if (description)
    {
      script_id(60408);
      script_version("1.6");
      script_cvs_date("Date: 2019/10/25 13:36:17");
    
      script_cve_id("CVE-2007-5495", "CVE-2007-5496");
    
      script_name(english:"Scientific Linux Security Update : setroubleshoot on SL5.x i386/x86_64");
      script_summary(english:"Checks rpm output for the updated packages");
    
      script_set_attribute(
        attribute:"synopsis", 
        value:
    "The remote Scientific Linux host is missing one or more security
    updates."
      );
      script_set_attribute(
        attribute:"description", 
        value:
    "A flaw was found in the way sealert wrote diagnostic messages to a
    temporary file. A local unprivileged user could perform a symbolic
    link attack, and cause arbitrary files, writable by other users, to be
    overwritten when a victim runs sealert. (CVE-2007-5495)
    
    A flaw was found in the way sealert displayed records from the
    setroubleshoot database as unescaped HTML. An local unprivileged
    attacker could cause AVC denial events with carefully crafted process
    or file names, injecting arbitrary HTML tags into the logs, which
    could be used as a scripting attack, or to confuse the user running
    sealert. (CVE-2007-5496)
    
    Additionally, the following bugs have been fixed in these update
    packages :
    
      - in certain situations, the sealert process used
        excessive CPU. These alerts are now capped at a maximum
        of 30, D-Bus is used instead of polling, threads causing
        excessive wake-up have been removed, and more robust
        exception-handling has been added.
    
      - different combinations of the sealert '-a', '-l', '-H',
        and '-v' options did not work as documented.
    
      - the SETroubleShoot browser did not allow multiple
        entries to be deleted.
    
      - the SETroubleShoot browser did not display statements
        that displayed whether SELinux was using Enforcing or
        Permissive mode, particularly when warning about SELinux
        preventions.
    
      - in certain cases, the SETroubleShoot browser gave
        incorrect instructions regarding paths, and would not
        display the full paths to files.
    
      - adding an email recipient to the recipients option from
        the /etc/setroubleshoot/setroubleshoot.cfg file and then
        generating an SELinux denial caused a traceback error.
        The recipients option has been removed; email addresses
        are now managed through the SETroubleShoot browser by
        navigating to File -> Edit Email Alert List, or by
        editing the
        /var/lib/setroubleshoot/email_alert_recipients file.
    
      - the setroubleshoot browser incorrectly displayed a
        period between the httpd_sys_content_t context and the
        directory path.
    
      - on the PowerPC architecture, The get_credentials()
        function in access_control.py would generate an
        exception when it called the socket.getsockopt()
        function.
    
      - The code which handles path information has been
        completely rewritten so that assumptions on path
        information which were misleading are no longer made. If
        the path information is not present, it will be
        presented as '<Unknown>'.
    
      - setroubleshoot had problems with non-English locales
        under certain circumstances, possibly causing a python
        traceback, an sealert window pop-up containing an error,
        a 'RuntimeError: maximum recursion depth exceeded' error
        after a traceback, or a 'UnicodeEncodeError' after a
        traceback.
    
      - sealert ran even when SELinux was disabled, causing
        'attempt to open server connection failed' errors.
        Sealert now checks whether SELinux is enabled or
        disabled.
    
      - the database setroubleshoot maintains was
        world-readable. The setroubleshoot database is now mode
        600, and is owned by the root user and group.
    
      - setroubleshoot did not validate requests to set AVC
        filtering options for users. In these updated packages,
        checks ensure that requests originate from the filter
        owner.
    
      - the previous setroubleshoot packages required a number
        of GNOME packages and libraries. setroubleshoot has
        therefore been split into 2 packages: setroubleshoot and
        setroubleshoot-server.
    
      - a bug in decoding the audit field caused an 'Input is
        not proper UTF-8, indicate encoding!' error message. The
        decoding code has been rewritten.
    
      - a file name mismatch in the setroubleshoot init script
        would cause a failure to shut down."
      );
      # https://listserv.fnal.gov/scripts/wa.exe?A2=ind0805&L=scientific-linux-errata&T=0&P=2172
      script_set_attribute(
        attribute:"see_also",
        value:"http://www.nessus.org/u?ddd3a9fc"
      );
      script_set_attribute(
        attribute:"solution", 
        value:
    "Update the affected setroubleshoot, setroubleshoot-plugins and / or
    setroubleshoot-server packages."
      );
      script_set_cvss_base_vector("CVSS2#AV:L/AC:M/Au:N/C:P/I:P/A:P");
      script_cwe_id(59, 79);
    
      script_set_attribute(attribute:"plugin_type", value:"local");
      script_set_attribute(attribute:"cpe", value:"x-cpe:/o:fermilab:scientific_linux");
    
      script_set_attribute(attribute:"vuln_publication_date", value:"2008/05/23");
      script_set_attribute(attribute:"patch_publication_date", value:"2008/05/21");
      script_set_attribute(attribute:"plugin_publication_date", value:"2012/08/01");
      script_set_attribute(attribute:"generated_plugin", value:"current");
      script_end_attributes();
    
      script_category(ACT_GATHER_INFO);
      script_copyright(english:"This script is Copyright (C) 2012-2019 and is owned by Tenable, Inc. or an Affiliate thereof.");
      script_family(english:"Scientific Linux Local Security Checks");
    
      script_dependencies("ssh_get_info.nasl");
      script_require_keys("Host/local_checks_enabled", "Host/cpu", "Host/RedHat/release", "Host/RedHat/rpm-list");
    
      exit(0);
    }
    
    
    include("audit.inc");
    include("global_settings.inc");
    include("rpm.inc");
    
    
    if (!get_kb_item("Host/local_checks_enabled")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);
    release = get_kb_item("Host/RedHat/release");
    if (isnull(release) || "Scientific Linux " >!< release) audit(AUDIT_HOST_NOT, "running Scientific Linux");
    if (!get_kb_item("Host/RedHat/rpm-list")) audit(AUDIT_PACKAGE_LIST_MISSING);
    
    cpu = get_kb_item("Host/cpu");
    if (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);
    if (cpu >!< "x86_64" && cpu !~ "^i[3-6]86$") audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, "Scientific Linux", cpu);
    
    
    flag = 0;
    if (rpm_check(release:"SL5", reference:"setroubleshoot-2.0.5-3.el5")) flag++;
    if (rpm_check(release:"SL5", reference:"setroubleshoot-plugins-2.0.4-2.el5")) flag++;
    if (rpm_check(release:"SL5", reference:"setroubleshoot-server-2.0.5-3.el5")) flag++;
    
    
    if (flag)
    {
      if (report_verbosity > 0) security_warning(port:0, extra:rpm_report_get());
      else security_warning(0);
      exit(0);
    }
    else audit(AUDIT_HOST_NOT, "affected");
    
  • NASL familyRed Hat Local Security Checks
    NASL idREDHAT-RHSA-2008-0061.NASL
    descriptionUpdated setroubleshoot packages that fix two security issues and several bugs are now available for Red Hat Enterprise Linux 5. This update has been rated as having moderate security impact by the Red Hat Security Response Team. The setroubleshoot packages provide tools to help diagnose SELinux problems. When AVC messages occur, an alert is generated that gives information about the problem, and how to create a resolution. A flaw was found in the way sealert wrote diagnostic messages to a temporary file. A local unprivileged user could perform a symbolic link attack, and cause arbitrary files, writable by other users, to be overwritten when a victim runs sealert. (CVE-2007-5495) A flaw was found in the way sealert displayed records from the setroubleshoot database as unescaped HTML. An local unprivileged attacker could cause AVC denial events with carefully crafted process or file names, injecting arbitrary HTML tags into the logs, which could be used as a scripting attack, or to confuse the user running sealert. (CVE-2007-5496) Additionally, the following bugs have been fixed in these update packages : * in certain situations, the sealert process used excessive CPU. These alerts are now capped at a maximum of 30, D-Bus is used instead of polling, threads causing excessive wake-up have been removed, and more robust exception-handling has been added. * different combinations of the sealert
    last seen2020-06-01
    modified2020-06-02
    plugin id32419
    published2008-05-22
    reporterThis script is Copyright (C) 2008-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
    sourcehttps://www.tenable.com/plugins/nessus/32419
    titleRHEL 5 : setroubleshoot (RHSA-2008:0061)
    code
    #%NASL_MIN_LEVEL 80502
    #
    # (C) Tenable Network Security, Inc.
    #
    # The descriptive text and package checks in this plugin were  
    # extracted from Red Hat Security Advisory RHSA-2008:0061. The text 
    # itself is copyright (C) Red Hat, Inc.
    #
    
    include("compat.inc");
    
    if (description)
    {
      script_id(32419);
      script_version ("1.23");
      script_cvs_date("Date: 2019/10/25 13:36:13");
    
      script_cve_id("CVE-2007-5495", "CVE-2007-5496");
      script_xref(name:"RHSA", value:"2008:0061");
    
      script_name(english:"RHEL 5 : setroubleshoot (RHSA-2008:0061)");
      script_summary(english:"Checks the rpm output for the updated packages");
    
      script_set_attribute(
        attribute:"synopsis", 
        value:"The remote Red Hat host is missing one or more security updates."
      );
      script_set_attribute(
        attribute:"description", 
        value:
    "Updated setroubleshoot packages that fix two security issues and
    several bugs are now available for Red Hat Enterprise Linux 5.
    
    This update has been rated as having moderate security impact by the
    Red Hat Security Response Team.
    
    The setroubleshoot packages provide tools to help diagnose SELinux
    problems. When AVC messages occur, an alert is generated that gives
    information about the problem, and how to create a resolution.
    
    A flaw was found in the way sealert wrote diagnostic messages to a
    temporary file. A local unprivileged user could perform a symbolic
    link attack, and cause arbitrary files, writable by other users, to be
    overwritten when a victim runs sealert. (CVE-2007-5495)
    
    A flaw was found in the way sealert displayed records from the
    setroubleshoot database as unescaped HTML. An local unprivileged
    attacker could cause AVC denial events with carefully crafted process
    or file names, injecting arbitrary HTML tags into the logs, which
    could be used as a scripting attack, or to confuse the user running
    sealert. (CVE-2007-5496)
    
    Additionally, the following bugs have been fixed in these update
    packages :
    
    * in certain situations, the sealert process used excessive CPU. These
    alerts are now capped at a maximum of 30, D-Bus is used instead of
    polling, threads causing excessive wake-up have been removed, and more
    robust exception-handling has been added.
    
    * different combinations of the sealert '-a', '-l', '-H', and '-v'
    options did not work as documented.
    
    * the SETroubleShoot browser did not allow multiple entries to be
    deleted.
    
    * the SETroubleShoot browser did not display statements that displayed
    whether SELinux was using Enforcing or Permissive mode, particularly
    when warning about SELinux preventions.
    
    * in certain cases, the SETroubleShoot browser gave incorrect
    instructions regarding paths, and would not display the full paths to
    files.
    
    * adding an email recipient to the recipients option from the
    /etc/setroubleshoot/setroubleshoot.cfg file and then generating an
    SELinux denial caused a traceback error. The recipients option has
    been removed; email addresses are now managed through the
    SETroubleShoot browser by navigating to File -> Edit Email Alert List,
    or by editing the /var/lib/setroubleshoot/email_alert_recipients file.
    
    * the setroubleshoot browser incorrectly displayed a period between
    the httpd_sys_content_t context and the directory path.
    
    * on the PowerPC architecture, The get_credentials() function in
    access_control.py would generate an exception when it called the
    socket.getsockopt() function.
    
    * The code which handles path information has been completely
    rewritten so that assumptions on path information which were
    misleading are no longer made. If the path information is not present,
    it will be presented as '<Unknown>'.
    
    * setroubleshoot had problems with non-English locales under certain
    circumstances, possibly causing a python traceback, an sealert window
    pop-up containing an error, a 'RuntimeError: maximum recursion depth
    exceeded' error after a traceback, or a 'UnicodeEncodeError' after a
    traceback.
    
    * sealert ran even when SELinux was disabled, causing 'attempt to open
    server connection failed' errors. Sealert now checks whether SELinux
    is enabled or disabled.
    
    * the database setroubleshoot maintains was world-readable. The
    setroubleshoot database is now mode 600, and is owned by the root user
    and group.
    
    * setroubleshoot did not validate requests to set AVC filtering
    options for users. In these updated packages, checks ensure that
    requests originate from the filter owner.
    
    * the previous setroubleshoot packages required a number of GNOME
    packages and libraries. setroubleshoot has therefore been split into 2
    packages: setroubleshoot and setroubleshoot-server.
    
    * a bug in decoding the audit field caused an 'Input is not proper
    UTF-8, indicate encoding!' error message. The decoding code has been
    rewritten.
    
    * a file name mismatch in the setroubleshoot init script would cause a
    failure to shut down.
    
    Users of setroubleshoot are advised to upgrade to these updated
    packages, which resolve these issues."
      );
      script_set_attribute(
        attribute:"see_also",
        value:"https://access.redhat.com/security/cve/cve-2007-5495"
      );
      script_set_attribute(
        attribute:"see_also",
        value:"https://access.redhat.com/security/cve/cve-2007-5496"
      );
      script_set_attribute(
        attribute:"see_also",
        value:"https://access.redhat.com/errata/RHSA-2008:0061"
      );
      script_set_attribute(
        attribute:"solution", 
        value:
    "Update the affected setroubleshoot, setroubleshoot-plugins and / or
    setroubleshoot-server packages."
      );
      script_set_cvss_base_vector("CVSS2#AV:L/AC:M/Au:N/C:P/I:P/A:P");
      script_cwe_id(59, 79);
    
      script_set_attribute(attribute:"plugin_type", value:"local");
      script_set_attribute(attribute:"cpe", value:"p-cpe:/a:redhat:enterprise_linux:setroubleshoot");
      script_set_attribute(attribute:"cpe", value:"p-cpe:/a:redhat:enterprise_linux:setroubleshoot-plugins");
      script_set_attribute(attribute:"cpe", value:"p-cpe:/a:redhat:enterprise_linux:setroubleshoot-server");
      script_set_attribute(attribute:"cpe", value:"cpe:/o:redhat:enterprise_linux:5");
    
      script_set_attribute(attribute:"vuln_publication_date", value:"2008/05/23");
      script_set_attribute(attribute:"patch_publication_date", value:"2008/05/21");
      script_set_attribute(attribute:"plugin_publication_date", value:"2008/05/22");
      script_set_attribute(attribute:"generated_plugin", value:"current");
      script_end_attributes();
    
      script_category(ACT_GATHER_INFO);
      script_copyright(english:"This script is Copyright (C) 2008-2019 and is owned by Tenable, Inc. or an Affiliate thereof.");
      script_family(english:"Red Hat Local Security Checks");
    
      script_dependencies("ssh_get_info.nasl");
      script_require_keys("Host/local_checks_enabled", "Host/RedHat/release", "Host/RedHat/rpm-list", "Host/cpu");
    
      exit(0);
    }
    
    
    include("audit.inc");
    include("global_settings.inc");
    include("misc_func.inc");
    include("rpm.inc");
    
    if (!get_kb_item("Host/local_checks_enabled")) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);
    release = get_kb_item("Host/RedHat/release");
    if (isnull(release) || "Red Hat" >!< release) audit(AUDIT_OS_NOT, "Red Hat");
    os_ver = pregmatch(pattern: "Red Hat Enterprise Linux.*release ([0-9]+(\.[0-9]+)?)", string:release);
    if (isnull(os_ver)) audit(AUDIT_UNKNOWN_APP_VER, "Red Hat");
    os_ver = os_ver[1];
    if (! preg(pattern:"^5([^0-9]|$)", string:os_ver)) audit(AUDIT_OS_NOT, "Red Hat 5.x", "Red Hat " + os_ver);
    
    if (!get_kb_item("Host/RedHat/rpm-list")) audit(AUDIT_PACKAGE_LIST_MISSING);
    
    cpu = get_kb_item("Host/cpu");
    if (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);
    if ("x86_64" >!< cpu && cpu !~ "^i[3-6]86$" && "s390" >!< cpu) audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, "Red Hat", cpu);
    
    yum_updateinfo = get_kb_item("Host/RedHat/yum-updateinfo");
    if (!empty_or_null(yum_updateinfo)) 
    {
      rhsa = "RHSA-2008:0061";
      yum_report = redhat_generate_yum_updateinfo_report(rhsa:rhsa);
      if (!empty_or_null(yum_report))
      {
        security_report_v4(
          port       : 0,
          severity   : SECURITY_WARNING,
          extra      : yum_report 
        );
        exit(0);
      }
      else
      {
        audit_message = "affected by Red Hat security advisory " + rhsa;
        audit(AUDIT_OS_NOT, audit_message);
      }
    }
    else
    {
      flag = 0;
      if (rpm_check(release:"RHEL5", reference:"setroubleshoot-2.0.5-3.el5")) flag++;
      if (rpm_check(release:"RHEL5", reference:"setroubleshoot-plugins-2.0.4-2.el5")) flag++;
      if (rpm_check(release:"RHEL5", reference:"setroubleshoot-server-2.0.5-3.el5")) flag++;
    
      if (flag)
      {
        security_report_v4(
          port       : 0,
          severity   : SECURITY_WARNING,
          extra      : rpm_report_get() + redhat_report_package_caveat()
        );
        exit(0);
      }
      else
      {
        tested = pkg_tests_get();
        if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);
        else audit(AUDIT_PACKAGE_NOT_INSTALLED, "setroubleshoot / setroubleshoot-plugins / setroubleshoot-server");
      }
    }
    

Oval

accepted2013-04-29T04:05:49.919-04:00
classvulnerability
contributors
  • nameAharon Chernin
    organizationSCAP.com, LLC
  • nameDragos Prisaca
    organizationG2, Inc.
definition_extensions
  • commentThe operating system installed on the system is Red Hat Enterprise Linux 5
    ovaloval:org.mitre.oval:def:11414
  • commentThe operating system installed on the system is CentOS Linux 5.x
    ovaloval:org.mitre.oval:def:15802
  • commentOracle Linux 5.x
    ovaloval:org.mitre.oval:def:15459
descriptionCross-site scripting (XSS) vulnerability in setroubleshoot 2.0.5 allows local users to inject arbitrary web script or HTML via a crafted (1) file or (2) process name, which triggers an Access Vector Cache (AVC) log entry in a log file used during composition of HTML documents for sealert.
familyunix
idoval:org.mitre.oval:def:10455
statusaccepted
submitted2010-07-09T03:56:16-04:00
titleCross-site scripting (XSS) vulnerability in setroubleshoot 2.0.5 allows local users to inject arbitrary web script or HTML via a crafted (1) file or (2) process name, which triggers an Access Vector Cache (AVC) log entry in a log file used during composition of HTML documents for sealert.
version18

Redhat

advisories
bugzilla
id436564
titlesocket.getsockopt() on ppc generates exception
oval
OR
  • commentRed Hat Enterprise Linux must be installed
    ovaloval:com.redhat.rhba:tst:20070304026
  • AND
    • commentRed Hat Enterprise Linux 5 is installed
      ovaloval:com.redhat.rhba:tst:20070331005
    • OR
      • AND
        • commentsetroubleshoot-plugins is earlier than 0:2.0.4-2.el5
          ovaloval:com.redhat.rhsa:tst:20080061001
        • commentsetroubleshoot-plugins is signed with Red Hat redhatrelease key
          ovaloval:com.redhat.rhsa:tst:20080061002
      • AND
        • commentsetroubleshoot is earlier than 0:2.0.5-3.el5
          ovaloval:com.redhat.rhsa:tst:20080061003
        • commentsetroubleshoot is signed with Red Hat redhatrelease key
          ovaloval:com.redhat.rhsa:tst:20080061004
      • AND
        • commentsetroubleshoot-server is earlier than 0:2.0.5-3.el5
          ovaloval:com.redhat.rhsa:tst:20080061005
        • commentsetroubleshoot-server is signed with Red Hat redhatrelease key
          ovaloval:com.redhat.rhsa:tst:20080061006
rhsa
idRHSA-2008:0061
released2008-05-21
severityModerate
titleRHSA-2008:0061: setroubleshoot security and bug fix update (Moderate)
rpms
  • setroubleshoot-0:2.0.5-3.el5
  • setroubleshoot-plugins-0:2.0.4-2.el5
  • setroubleshoot-server-0:2.0.5-3.el5