CVE-2013-3712 Weak cryptography in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2013-3712 and fix it if it is affected.
What it is: CVE-2013-3712 is a critical vulnerability in n/a, published on 26 Feb 2014.
Exploitation: There is no known exploitation of CVE-2013-3712 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2013-3712/ (Markdown: https://insights.sbomify.com/CVE-2013-3712/index.md)
SUSE Studio Onsite uses static secret tokens, potentially allowing attackers to bypass security controls or impersonate users.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2013-3712?
CVE-2013-3712 is a critical vulnerability in n/a, published on 26 Feb 2014.
Official description
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.
Weakness: CWE-310
Which versions are affected by CVE-2013-3712?
It affects 2 products.
Products include Suse Studio Extension for System Z, Suse Studio Onsite.
How do I fix CVE-2013-3712?
No fix has been published for CVE-2013-3712 yet. Limit exposure of the affected software until one is available.
Is CVE-2013-3712 being exploited?
There is no known exploitation of CVE-2013-3712 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-vxw2-5mh8-c5c6.