openCryptoki file symlink

opencryptoki-file-symlink (78943) The risk level is classified as MediumMedium Risk

Description:

openCryptoki could allow a local attacker to launch a symlink attack. Temporary files are created insecurely. A local attacker could exploit this vulnerability by creating a symbolic link from the /var/tmp temporary file to various files on the system, which could allow the attacker to overwrite arbitrary files on the system with elevated privileges.

*CVSS:

Base Score: 3.3
  Access Vector: Local
  Access Complexity: Medium
  Authentication: None
  Confidentiality Impact: None
  Integrity Impact: Partial
  Availability Impact: Partial
 
Temporal Score: 2.9
  Exploitability: High
  Remediation Level: Official-Fix
  Report Confidence: Confirmed

Consequences:

File Manipulation

Remedy:

Upgrade to the latest version of openCryptoki (2.4.2 or later), available from the openCryptoki Web site. See References.

References:

  • openCryptoki Web site: openCryptoki.
  • oss-security: Raphael Geissert | 6 Sep: CVE request: opencryptoki insecure lock files handling .
  • Red Hat Bugzilla Bug 730636: CVE-2012-4454 CVE-2012-4455 opencryptoki: insecure handling of files in the /tmp directory.
  • BID-55627: openCryptoki Multiple Insecure File Creation Vulnerabilities
  • CVE-2012-4455: openCryptoki 2.4.1 allows local users to create or set world-writable permissions on arbitrary files via a symlink attack on the (1) LCK..opencryptoki or (2) LCK..opencryptoki_stdll file in /var/lock/.
  • SA50702: openCryptoki Insecure Temporary File Security Issue

Platforms Affected:

  • openCryptoki openCryptoki 2.4.1

Reported:

Sep 27, 2012

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this

Return to the main page