Home page logo
/

bugtraq logo Bugtraq mailing list archives

SYMSA-2006-008:Password Safe - Lock Password Database Configuration Not Enforced
From: research () symantec com
Date: 21 Jul 2006 18:44:06 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1




                   Symantec Vulnerability Research
                   http://www.symantec.com/research
                         Security Advisory

   Advisory ID: SYMSA-2006-008
Advisory Title: Password Safe - Lock Password Database Configuration Not Enforced
        Author: J.R. Wikes
  Release Date: 07-24-2006
   Application: Password Safe 2.11, 2.16, 3.0BETA1
      Platform: Windows (95/98/NT/2000/XP)
      Severity: Locally exploitable
 Vendor status: Verified by vendor.  Upgrade available
    CVE Number: CVE-2006-3675
    Reference: http://www.securityfocus.com/bid/19078

Overview:

Password Safe is open source software which allows users to
create a secured and encrypted master password list. This list
is controlled and accessed through the Password Safe software
resident on a user’s workstation.

One of the security features of the software allows users to
configure the password database to lock upon the workstation
being locked or after a set period of inactivity. It was
determined that this locking feature is not enforced on either
of these events when certain dialogue windows are open in the
software.

More information on Password Safe can be obtained at
http://passwordsafe.sourceforge.net/.

Details:

Password Safe can be configured to lock the password database
when the workstation is locked or after a set period of idle
time to prevent unauthorized access to the database contents.
When the following dialogue windows are left open in the
application the database will not lock on either of these
preconfigured events.

File > New Database
File > Open Database
File > Save As
File > Export To
File > Import From
File > Merge Database
Edit > Add Entry
Edit > Edit/View Entry
Manage > Change Safe Combination
Manage > Make Backup
Manage > Restore from Backup
Help > About Password Safe

By not locking the password database as configured, its contents
may be at risk of compromise by an attacker with access to the
workstation.

Vendor Response:

        The above vulnerability was addressed for the affected
        platforms in Password Safe 3.01.

        Customers can download the latest version of Password
        Safe from the following website:


        https://sourceforge.net/projects/passwordsafe/

        If there are any further questions about this statement,
        please contact ronys () users sourceforge net 

Recommendation:

        Follow your organization's testing procedures before
        applying patches or workarounds.  Customers should
        upgrade to Password Safe 3.01, or higher as soon as
        possible.

Common Vulnerabilities and Exposures (CVE) Information:

The Common Vulnerabilities and Exposures (CVE) project has
assigned the following names to these issues.  These are
candidates for inclusion in the CVE list
(http://cve.mitre.org), which standardizes names for security
problems.


  CVE-2006-3675

- -------Symantec Vulnerability Research Advisory Information-------

For questions about this advisory, or to report an error:
research () symantec com

For details on Symantec's Vulnerability Reporting Policy:
http://www.symantec.com/research/Symantec-Responsible-Disclosure.pdf

Symantec Vulnerability Research Advisory Archive:
http://www.symantec.com/research/

Symantec Vulnerability Research GPG Key:
http://www.symantec.com/research/Symantec_Consulting_Services_Advisories_GPG.asc

- -------------Symantec Product Advisory Information-------------

To Report a Security Vulnerability in a Symantec Product:
secure () symantec com

For general information on Symantec's Product Vulnerability
reporting and response:
http://www.symantec.com/security/

Symantec Product Advisory Archive:
http://www.symantec.com/avcenter/security/SymantecAdvisories.html

Symantec Product Advisory PGP Key:
http://www.symantec.com/security/Symantec-Vulnerability-Management-Key.asc

- ---------------------------------------------------------------

Copyright (c) 2006 by Symantec Corp
Permission to redistribute this alert electronically is granted
as long as it is not edited in any way unless authorized by
Symantec Consulting Services. Reprinting the whole or part of
this alert in any medium other than electronically requires
permission from cs_advisories () symantec com 

Disclaimer
The information in the advisory is believed to be accurate at the
time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS
condition. There are no warranties with regard to this information.
Neither the author nor the publisher accepts any liability for any
direct, indirect, or consequential loss or damage arising from use
of, or reliance on, this information.

Symantec, Symantec products, and Symantec Consulting Services are
registered trademarks of Symantec Corp. and/or affiliated companies
in the United States and other countries. All other registered and
unregistered trademarks represented in this document are the sole
property of their respective companies/owners.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)

iD8DBQFEwSEmuk7IIFI45IARAjj0AKDczBDqi2cHgO4IoiGrisEy0Hu4nwCeMuyh
CMZesdTEK1BizW6euMxJVHk=
=iRbL
-----END PGP SIGNATURE-----


  By Date           By Thread  

Current thread:
  • SYMSA-2006-008:Password Safe - Lock Password Database Configuration Not Enforced research (Jul 24)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault