ID CVE-2007-3852
Summary The init script (sysstat.in) in sysstat 5.1.2 up to 7.1.6 creates /tmp/sysstat.run insecurely, which allows local users to execute arbitrary code.
References
Vulnerable Configurations
  • cpe:2.3:a:sysstat:sysstat:5.1.2
    cpe:2.3:a:sysstat:sysstat:5.1.2
  • cpe:2.3:a:sysstat:sysstat:5.1.3
    cpe:2.3:a:sysstat:sysstat:5.1.3
  • cpe:2.3:a:sysstat:sysstat:5.1.4
    cpe:2.3:a:sysstat:sysstat:5.1.4
  • cpe:2.3:a:sysstat:sysstat:5.1.5
    cpe:2.3:a:sysstat:sysstat:5.1.5
  • cpe:2.3:a:sysstat:sysstat:6.0.0
    cpe:2.3:a:sysstat:sysstat:6.0.0
  • cpe:2.3:a:sysstat:sysstat:6.0.1
    cpe:2.3:a:sysstat:sysstat:6.0.1
  • cpe:2.3:a:sysstat:sysstat:6.0.2
    cpe:2.3:a:sysstat:sysstat:6.0.2
  • cpe:2.3:a:sysstat:sysstat:6.0.3
    cpe:2.3:a:sysstat:sysstat:6.0.3
  • cpe:2.3:a:sysstat:sysstat:6.0.4
    cpe:2.3:a:sysstat:sysstat:6.0.4
  • cpe:2.3:a:sysstat:sysstat:6.0.5
    cpe:2.3:a:sysstat:sysstat:6.0.5
  • cpe:2.3:a:sysstat:sysstat:7.0.0
    cpe:2.3:a:sysstat:sysstat:7.0.0
  • cpe:2.3:a:sysstat:sysstat:7.0.1
    cpe:2.3:a:sysstat:sysstat:7.0.1
  • cpe:2.3:a:sysstat:sysstat:7.0.2
    cpe:2.3:a:sysstat:sysstat:7.0.2
  • cpe:2.3:a:sysstat:sysstat:7.0.3
    cpe:2.3:a:sysstat:sysstat:7.0.3
  • cpe:2.3:a:sysstat:sysstat:7.0.4
    cpe:2.3:a:sysstat:sysstat:7.0.4
  • cpe:2.3:a:sysstat:sysstat:7.1.1
    cpe:2.3:a:sysstat:sysstat:7.1.1
  • cpe:2.3:a:sysstat:sysstat:7.1.2
    cpe:2.3:a:sysstat:sysstat:7.1.2
  • cpe:2.3:a:sysstat:sysstat:7.1.3
    cpe:2.3:a:sysstat:sysstat:7.1.3
  • cpe:2.3:a:sysstat:sysstat:7.1.4
    cpe:2.3:a:sysstat:sysstat:7.1.4
  • cpe:2.3:a:sysstat:sysstat:7.1.5
    cpe:2.3:a:sysstat:sysstat:7.1.5
  • cpe:2.3:a:sysstat:sysstat:7.1.6
    cpe:2.3:a:sysstat:sysstat:7.1.6
CVSS
Base: 4.4 (as of 14-08-2007 - 15:05)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
LOCAL MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2011-1005.NASL
    description An updated sysstat package that fixes one security issue, various bugs, and adds one enhancement is now available for Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The sysstat package contains a set of utilities which enable system monitoring of disks, network, and other I/O activity. It was found that the sysstat initscript created a temporary file in an insecure way. A local attacker could use this flaw to create arbitrary files via a symbolic link attack. (CVE-2007-3852) This update fixes the following bugs : * On systems under heavy load, the sadc utility would sometimes output the following error message if a write() call was unable to write all of the requested input : 'Cannot write data to system activity file: Success.' In this updated package, the sadc utility tries to write the remaining input, resolving this issue. (BZ#454617) * On the Itanium architecture, the 'sar -I' command provided incorrect information about the interrupt statistics of the system. With this update, the 'sar -I' command has been disabled for this architecture, preventing this bug. (BZ#468340) * Previously, the 'iostat -n' command used invalid data to create statistics for read and write operations. With this update, the data source for these statistics has been fixed, and the iostat utility now returns correct information. (BZ#484439) * The 'sar -d' command used to output invalid data about block devices. With this update, the sar utility recognizes disk registration and disk overflow statistics properly, and only correct and relevant data is now displayed. (BZ#517490) * Previously, the sar utility set the maximum number of days to be logged in one month too high. Consequently, data from a month was appended to data from the preceding month. With this update, the maximum number of days has been set to 25, and data from a month now correctly replaces data from the preceding month. (BZ#578929) * In previous versions of the iostat utility, the number of NFS mount points was hard-coded. Consequently, various issues occurred while iostat was running and NFS mount points were mounted or unmounted; certain values in iostat reports overflowed and some mount points were not reported at all. With this update, iostat properly recognizes when an NFS mount point mounts or unmounts, fixing these issues. (BZ#675058, BZ#706095, BZ#694767) * When a device name was longer than 13 characters, the iostat utility printed a redundant new line character, making its output less readable. This bug has been fixed and now, no extra characters are printed if a long device name occurs in iostat output. (BZ#604637) * Previously, if kernel interrupt counters overflowed, the sar utility provided confusing output. This bug has been fixed and the sum of interrupts is now reported correctly. (BZ#622557) * When some processors were disabled on a multi-processor system, the sar utility sometimes failed to provide information about the CPU activity. With this update, the uptime of a single processor is used to compute the statistics, rather than the total uptime of all processors, and this bug no longer occurs. (BZ#630559) * Previously, the mpstat utility wrongly interpreted data about processors in the system. Consequently, it reported a processor that did not exist. This bug has been fixed and non-existent CPUs are no longer reported by mpstat. (BZ#579409) * Previously, there was no easy way to enable the collection of statistics about disks and interrupts. Now, the SADC_OPTIONS variable can be used to set parameters for the sadc utility, fixing this bug. (BZ#598794) * The read_uptime() function failed to close its open file upon exit. A patch has been provided to fix this bug. (BZ#696672) This update also adds the following enhancement : * With this update, the cifsiostat utility has been added to the sysstat package to provide CIFS (Common Internet File System) mount point I/O statistics. (BZ#591530) All sysstat users are advised to upgrade to this updated package, which contains backported patches to correct these issues and add this enhancement.
    last seen 2019-02-21
    modified 2018-11-26
    plugin id 55644
    published 2011-07-22
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=55644
    title RHEL 5 : sysstat (RHSA-2011:1005)
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20110721_SYSSTAT_ON_SL5_X.NASL
    description The sysstat package contains a set of utilities which enable system monitoring of disks, network, and other I/O activity. It was found that the sysstat initscript created a temporary file in an insecure way. A local attacker could use this flaw to create arbitrary files via a symbolic link attack. (CVE-2007-3852) This update fixes the following bugs : - On systems under heavy load, the sadc utility would sometimes output the following error message if a write() call was unable to write all of the requested input : 'Cannot write data to system activity file: Success.' In this updated package, the sadc utility tries to write the remaining input, resolving this issue. - On the Itanium architecture, the 'sar -I' command provided incorrect information about the interrupt statistics of the system. With this update, the 'sar -I' command has been disabled for this architecture, preventing this bug. - Previously, the 'iostat -n' command used invalid data to create statistics for read and write operations. With this update, the data source for these statistics has been fixed, and the iostat utility now returns correct information. - The 'sar -d' command used to output invalid data about block devices. With this update, the sar utility recognizes disk registration and disk overflow statistics properly, and only correct and relevant data is now displayed. - Previously, the sar utility set the maximum number of days to be logged in one month too high. Consequently, data from a month was appended to data from the preceding month. With this update, the maximum number of days has been set to 25, and data from a month now correctly replaces data from the preceding month. - In previous versions of the iostat utility, the number of NFS mount points was hard-coded. Consequently, various issues occurred while iostat was running and NFS mount points were mounted or unmounted; certain values in iostat reports overflowed and some mount points were not reported at all. With this update, iostat properly recognizes when an NFS mount point mounts or unmounts, fixing these issues. - When a device name was longer than 13 characters, the iostat utility printed a redundant new line character, making its output less readable. This bug has been fixed and now, no extra characters are printed if a long device name occurs in iostat output. - Previously, if kernel interrupt counters overflowed, the sar utility provided confusing output. This bug has been fixed and the sum of interrupts is now reported correctly. - When some processors were disabled on a multi-processor system, the sar utility sometimes failed to provide information about the CPU activity. With this update, the uptime of a single processor is used to compute the statistics, rather than the total uptime of all processors, and this bug no longer occurs. - Previously, the mpstat utility wrongly interpreted data about processors in the system. Consequently, it reported a processor that did not exist. This bug has been fixed and non-existent CPUs are no longer reported by mpstat. - Previously, there was no easy way to enable the collection of statistics about disks and interrupts. Now, the SADC_OPTIONS variable can be used to set parameters for the sadc utility, fixing this bug. - The read_uptime() function failed to close its open file upon exit. A patch has been provided to fix this bug. This update also adds the following enhancement : - With this update, the cifsiostat utility has been added to the sysstat package to provide CIFS (Common Internet File System) mount point I/O statistics. All sysstat users are advised to upgrade to this updated package, which contains backported patches to correct these issues and add this enhancement.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 61095
    published 2012-08-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=61095
    title Scientific Linux Security Update : sysstat on SL5.x i386/x86_64
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2007-1697.NASL
    description - Mon Aug 20 2007 Ivana Varekova - 7.0.4-3 - fix CVE-2007-3852 - sysstat insecure temporary file usage Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-10-21
    plugin id 27727
    published 2007-11-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=27727
    title Fedora 7 : sysstat-7.0.4-3.fc7 (2007-1697)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2011-1005.NASL
    description An updated sysstat package that fixes one security issue, various bugs, and adds one enhancement is now available for Red Hat Enterprise Linux 5. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The sysstat package contains a set of utilities which enable system monitoring of disks, network, and other I/O activity. It was found that the sysstat initscript created a temporary file in an insecure way. A local attacker could use this flaw to create arbitrary files via a symbolic link attack. (CVE-2007-3852) This update fixes the following bugs : * On systems under heavy load, the sadc utility would sometimes output the following error message if a write() call was unable to write all of the requested input : 'Cannot write data to system activity file: Success.' In this updated package, the sadc utility tries to write the remaining input, resolving this issue. (BZ#454617) * On the Itanium architecture, the 'sar -I' command provided incorrect information about the interrupt statistics of the system. With this update, the 'sar -I' command has been disabled for this architecture, preventing this bug. (BZ#468340) * Previously, the 'iostat -n' command used invalid data to create statistics for read and write operations. With this update, the data source for these statistics has been fixed, and the iostat utility now returns correct information. (BZ#484439) * The 'sar -d' command used to output invalid data about block devices. With this update, the sar utility recognizes disk registration and disk overflow statistics properly, and only correct and relevant data is now displayed. (BZ#517490) * Previously, the sar utility set the maximum number of days to be logged in one month too high. Consequently, data from a month was appended to data from the preceding month. With this update, the maximum number of days has been set to 25, and data from a month now correctly replaces data from the preceding month. (BZ#578929) * In previous versions of the iostat utility, the number of NFS mount points was hard-coded. Consequently, various issues occurred while iostat was running and NFS mount points were mounted or unmounted; certain values in iostat reports overflowed and some mount points were not reported at all. With this update, iostat properly recognizes when an NFS mount point mounts or unmounts, fixing these issues. (BZ#675058, BZ#706095, BZ#694767) * When a device name was longer than 13 characters, the iostat utility printed a redundant new line character, making its output less readable. This bug has been fixed and now, no extra characters are printed if a long device name occurs in iostat output. (BZ#604637) * Previously, if kernel interrupt counters overflowed, the sar utility provided confusing output. This bug has been fixed and the sum of interrupts is now reported correctly. (BZ#622557) * When some processors were disabled on a multi-processor system, the sar utility sometimes failed to provide information about the CPU activity. With this update, the uptime of a single processor is used to compute the statistics, rather than the total uptime of all processors, and this bug no longer occurs. (BZ#630559) * Previously, the mpstat utility wrongly interpreted data about processors in the system. Consequently, it reported a processor that did not exist. This bug has been fixed and non-existent CPUs are no longer reported by mpstat. (BZ#579409) * Previously, there was no easy way to enable the collection of statistics about disks and interrupts. Now, the SADC_OPTIONS variable can be used to set parameters for the sadc utility, fixing this bug. (BZ#598794) * The read_uptime() function failed to close its open file upon exit. A patch has been provided to fix this bug. (BZ#696672) This update also adds the following enhancement : * With this update, the cifsiostat utility has been added to the sysstat package to provide CIFS (Common Internet File System) mount point I/O statistics. (BZ#591530) All sysstat users are advised to upgrade to this updated package, which contains backported patches to correct these issues and add this enhancement.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 56263
    published 2011-09-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=56263
    title CentOS 5 : sysstat (CESA-2011:1005)
redhat via4
advisories
bugzilla
id 706095
title iostat -n - values in output overflows
oval
AND
  • comment Red Hat Enterprise Linux 5 is installed
    oval oval:com.redhat.rhsa:tst:20070055001
  • comment sysstat is earlier than 0:7.0.2-11.el5
    oval oval:com.redhat.rhsa:tst:20111005002
  • comment sysstat is signed with Red Hat redhatrelease key
    oval oval:com.redhat.rhsa:tst:20111005003
rhsa
id RHSA-2011:1005
released 2011-07-21
severity Low
title RHSA-2011:1005: sysstat security, bug fix, and enhancement update (Low)
rpms sysstat-0:7.0.2-11.el5
refmap via4
bid 25380
confirm https://bugs.gentoo.org/show_bug.cgi?id=188808
osvdb 39709
secunia 26527
xf sysstat-init-privilege-escalation(36045)
statements via4
contributor Joshua Bressers
lastmodified 2008-05-12
organization Red Hat
statement This issue did not affect the versions of sysstat as shipped with Red Hat Enterprise Linux 2.1, 3, or 4. For Red Hat Enterprise Linux 5, Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251200 The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw.
Last major update 25-08-2011 - 00:00
Published 14-08-2007 - 14:17
Last modified 28-07-2017 - 21:32
Back to Top