CVE-2013-6386 json
Drupal 6.x before 6.29 and 7.x before 7.24 uses the PHP mt_rand function to generate random numbers, which uses predictable seeds and allow…
published 12y ago modified 4mo ago also EUVD-2013-6211
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Drupal 6.x before 6.29 and 7.x before 7.24 uses the PHP mt_rand function to generate random numbers, which uses predictable seeds and allows remote attackers to predict security strings and bypass intended restrictions via a brute force attack.
Patch / fix
- drupal.org/SA-CORE-2013-003 advisory
Is CVE-2013-6386 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-6386 updated cvss 4.3
drupal: multiple vulnerabilities corrected in 6.29 and 7.24 (SA-CORE-2013-003)
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
drupal.org
/SA-CORE-2013-003
patch, vendor-advisory
-
debian.org
/security/2013/dsa-2828
vendor-advisory
-
debian.org
/security/2013/dsa-2804
vendor-advisory
-
secunia.com
/advisories/56148
third-party-advisory
-
openwall.com
/lists/oss-security/2013/11/22/4
mailing-list
Sources
- CVE List CVE-2013-6386
- NVD CVE-2013-6386
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.