First published: Wed Feb 26 2014(Updated: )
SUSE Studio Onsite 1.3.x before 1.3.6 and SUSE Studio Extension for System z 1.3 uses "static" secret tokens, which has unspecified impact and vectors.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
SUSE Studio | =1.3 | |
SUSE Studio | =1.3 | |
SUSE Studio | =1.3.1 | |
SUSE Studio | =1.3.2 | |
SUSE Studio | =1.3.3 | |
SUSE Studio | =1.3.4 | |
SUSE Studio | =1.3.5 | |
=1.3 | ||
=1.3 | ||
=1.3.1 | ||
=1.3.2 | ||
=1.3.3 | ||
=1.3.4 | ||
=1.3.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-3712 is currently unspecified, but it relates to the use of static secret tokens.
To fix CVE-2013-3712, update SUSE Studio Onsite to version 1.3.6 or later, or ensure the use of dynamic secret tokens.
CVE-2013-3712 affects SUSE Studio Onsite versions 1.3.x before 1.3.6 and SUSE Studio Extension for System z version 1.3.
CVE-2013-3712 may lead to potential unauthorized access due to the use of static secret tokens.
CVE-2013-3712 was disclosed in 2013 and pertains to vulnerabilities in specific versions of SUSE software.