CVE-2013-3709 json
WebYaST 1.3 uses weak permissions for config/initializers/secret_token.rb, which allows local users to gain privileges by reading the Rails…
published 12y ago modified 4mo ago also EUVD-2013-3642
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 41%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2013-3709 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- bugzilla.novell.com https://bugzilla.novell.com/show_bug.cgi?id=851116 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
bugzilla.novell.com
/show_bug.cgi?id=851116
exploit
-
lists.opensuse.org
/opensuse-security-announce/2013-12/msg00014.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2014-01/msg00001.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-12/msg00012.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-12/msg00013.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-12/msg00006.html
vendor-advisory
- github.com /rapid7/metasploit-framework/blob/master/modules/exploits/multi/http/rails_secret_deserialization.rb
Sources
- CVE List CVE-2013-3709
- NVD CVE-2013-3709
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.