CVE-2013-6658 json
Multiple use-after-free vulnerabilities in the layout implementation in Blink, as used in Google Chrome before 33.0.1750.117, allow remote…
published 12y ago modified 4mo ago also EUVD-2013-6460
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Multiple use-after-free vulnerabilities in the layout implementation in Blink, as used in Google Chrome before 33.0.1750.117, allow remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving (1) running JavaScript code during execution of the updateWidgetPositions function or (2) making a call into a plugin during execution of the updateWidgetPositions function.
Patch / fix
- google chrome 33.0.1750.117
- 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
Is CVE-2013-6658 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
2.35% chance of exploitation in the next 30 days, higher than 83% 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
-
debian.org
/security/2014/dsa-2883
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2014-03/msg00006.html
vendor-advisory
-
googlechromereleases.blogspot.com
/2014/02/stable-channel-update_20.html
vendor-advisory
- code.google.com /p/chromium/issues/detail?id=322891
- src.chromium.org /viewvc/blink?revision=165052&view=revision
Sources
- CVE List CVE-2013-6658
- NVD CVE-2013-6658
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.