# CVE-2013-3709: Information disclosure in n/a

> Local attackers can read the Rails secret token from a file with weak permissions to escalate privileges in WebYaST.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vr5h-9245-q2mh, SUSE-RU-2015:0793-1

## What is CVE-2013-3709?

CVE-2013-3709 is a high-severity vulnerability in n/a, published on 23 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WebYaST 1.3 uses weak permissions for config/initializers/secret_token.rb, which allows local users to gain privileges by reading the Rails secret token from this file.

Weakness: CWE-264

## Which versions are affected by CVE-2013-3709?

It affects 3 products.


Products: Novell Suse Lifecycle Management Server, Suse Studio Onsite, Suse Webyast.

## How do I fix CVE-2013-3709?

No fix has been published for CVE-2013-3709 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-3709 being exploited?

There is no known exploitation of CVE-2013-3709 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2013-7042](https://insights.sbomify.com/CVE-2013-7042/): Information disclosure in n/a (medium 4.6)
- [CVE-2013-3710](https://insights.sbomify.com/CVE-2013-3710/): Weak cryptography in n/a (medium 4.3)
- [CVE-2010-1325](https://insights.sbomify.com/CVE-2010-1325/): Cross-site request forgery in n/a (medium 4.3)
- [CVE-2011-0993](https://insights.sbomify.com/CVE-2011-0993/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3709 and fix it if it is affected.

What it is: CVE-2013-3709 is a high-severity vulnerability in n/a, published on 23 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-3709 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-3709/ (Markdown: https://insights.sbomify.com/CVE-2013-3709/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-3709
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-3709
- OSV: https://osv.dev/vulnerability/CVE-2013-3709

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-3709/
Summaries are generated and may contain mistakes; the official description above is the record.