CVE-2013-6624 json
Use-after-free vulnerability in Google Chrome before 31.0.1650.48 allows remote attackers to cause a denial of service or possibly have uns…
published 2013-11-13 12 y ago modified 2026-06-17 4 mo ago also EUVD-2013-6426
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in Google Chrome before 31.0.1650.48 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving the string values of id attributes.
Patch / fix
- google chrome 31.0.1650.48
- chromium openSUSE Tumbleweed 55.0.2883.75-3.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
opensuse advisories openSUSE-SU-2024:10171-1openSUSE-SU-2024:12948-1
Exploit prediction
1.46% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
- Technology feeds
References
-
lists.opensuse.org
/opensuse-updates/2014-01/msg00042.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-11/msg00025.html
vendor-advisory
-
debian.org
/security/2013/dsa-2799
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-12/msg00002.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-11/msg00026.html
vendor-advisory
-
googlechromereleases.blogspot.com
/2013/11/stable-channel-update.html
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19168
vdb-entry, signature
- code.google.com /p/chromium/issues/detail?id=290566
Sources
- CVE List CVE-2013-6624
- NVD CVE-2013-6624
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.