{"vuid":"VU#557062","idnumber":"557062","name":"CUPS stores user account details in plain text in log file","keywords":["information disclosure","plain text","/var/log/cups/error_log","Active Directory","CUPS","smb","samba"],"overview":"When an SMB printer is configured, CUPS stores plain text login information to the log file.","clean_desc":"CUPS is a cross-platform printing system for UNIX environments. It can use the IPP, LPD, SMB, and JetDirect protocols to interact with printers. The SMB protocol is used to communicate with printers that are shared via Microsoft Windows or other SMB-compatible software such as Samba. When an SMB printer is added or modified, the connection string for the printer is written to the log file in plain text. This connection string will contain a username and password if authentication is required for the printer.","impact":"A local authenticated user may be able to retrieve the usernames and passwords for other accounts.","resolution":"Apply a patch from your vendor\nFor vendor-specific information regarding vulnerable status and patch availability, please see the Systems Affected section of this document.","workarounds":"Upgrade your version of CUPS This issue is resolved in CUPS 1.1.22rc1. Starting with this version, the connection string for the printer is sanitized so that it does not contain sensitive information. Restrict access to the CUPS log file By default, the CUPS log file is world-readable. Access to the CUPS log file can be restricted by setting the LogFilePerm option in cupsd.conf to \"0600\" Do not use authenticated printing to Windows via Samba Because of the possibility of disclosing sensitive information when using a printer shared via SMB, it is suggested to use other protocols such as LPD. Windows can function as an LPD server when Print Services for UNIX is installed.","sysaffected":"","thanks":"Thanks to Gary Smith for reporting this vulnerability.","author":"This document was written by Will Dormann.","public":["http://www.securitytracker.com/alerts/2004/Oct/1011529.html","http://secunia.com/advisories/12736/","http://fedoranews.org/updates/FEDORA-2004-331.shtml","http://www.cups.org/ssr.html"],"cveids":["CVE-2004-0923"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2004-09-24T11:59:27Z","publicdate":"2004-10-05T00:00:00Z","datefirstpublished":"2004-11-19T21:09:29Z","dateupdated":"2004-12-17T19:05:51Z","revision":17,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"1","cam_exploitation":"0","cam_internetinfrastructure":"5","cam_population":"15","cam_impact":"15","cam_easeofexploitation":"20","cam_attackeraccessrequired":"10","cam_scorecurrent":"5.0625","cam_scorecurrentwidelyknown":"21.09375","cam_scorecurrentwidelyknownexploited":"37.96875","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":5.0625,"vulnote":null}