||The default configuration of su in /etc/pam.d/su in GNU coreutils 5.2.1 allows local users to gain the privileges of a (1) locked or (2) expired account by entering the account name on the command line, related to improper use of the pam_succeed_if.so module.
|Base: ||4.4 (as of 29-07-2008 - 13:17)|
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 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.
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.
|NASL family||Scientific Linux Local Security Checks |
|NASL id||SL_20080724_COREUTILS_ON_SL4_X.NASL |
|description||The coreutils packages were found to not use the pam_succeed_if Pluggable Authentication Module (PAM) correctly in the configuration file for the 'su' command. Any local user could use this command to change to a locked or expired user account if the target account's password was known to the user running 'su'. These updated packages, correctly, only allow the root user to switch to locked or expired accounts using 'su'. (CVE-2008-1946) |
|last seen||2019-02-21 |
|plugin id||60450 |
|title||Scientific Linux Security Update : coreutils on SL4.x i386/x86_64 |
|NASL family||Red Hat Local Security Checks |
|NASL id||REDHAT-RHSA-2008-0780.NASL |
|description||Updated coreutils packages that fix a security issue are now available for Red Hat Enterprise Linux 4.
This update has been rated as having low security impact by the Red Hat Security Response Team.
The coreutils package contains the core GNU utilities. It is the combination of the old GNU fileutils, sh-utils, and textutils packages.
The coreutils packages were found to not use the pam_succeed_if Pluggable Authentication Module (PAM) correctly in the configuration file for the 'su' command. Any local user could use this command to change to a locked or expired user account if the target account's password was known to the user running 'su'. These updated packages, correctly, only allow the root user to switch to locked or expired accounts using 'su'. (CVE-2008-1946)
All users of coreutils are advised to upgrade to this updated package, which resolve this issue. |
|last seen||2019-02-21 |
|plugin id||33586 |
|title||RHEL 4 : coreutils (RHSA-2008:0780) |
|name||Aharon Chernin |
|organization||SCAP.com, LLC |
|name||Dragos Prisaca |
|organization||G2, Inc. |
|comment||The operating system installed on the system is Red Hat Enterprise Linux 4 |
|comment||CentOS Linux 4.x |
|comment||Oracle Linux 4.x |
|description||The default configuration of su in /etc/pam.d/su in GNU coreutils 5.2.1 allows local users to gain the privileges of a (1) locked or (2) expired account by entering the account name on the command line, related to improper use of the pam_succeed_if.so module. |
|title||The default configuration of su in /etc/pam.d/su in GNU coreutils 5.2.1 allows local users to gain the privileges of a (1) locked or (2) expired account by entering the account name on the command line, related to improper use of the pam_succeed_if.so module. |
|title||CVE-2008-1946 /etc/pam.d/su is wrong in RHEL-4.6 |
|comment||Red Hat Enterprise Linux 4 is installed |
|comment||coreutils is earlier than 0:5.2.1-31.8.el4 |
|comment||coreutils is signed with Red Hat master key |
|title||RHSA-2008:0780: coreutils security update (Low) |
|Last major update
||21-08-2010 - 01:19
||28-07-2008 - 13:41
||28-09-2017 - 21:30