CVE-2013-2923 json
Multiple unspecified vulnerabilities in Google Chrome before 30.0.1599.66 allow attackers to cause a denial of service or possibly have oth…
published 13y ago modified 4mo ago also EUVD-2013-2862
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in Google Chrome before 30.0.1599.66 allow attackers to cause a denial of service or possibly have other impact via unknown vectors.
Patch / fix
- google chrome 30.0.1599.66
- 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-2923 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
1.33% chance of exploitation in the next 30 days, higher than 71% 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
- Technology feeds
References
-
lists.opensuse.org
/opensuse-updates/2014-01/msg00042.html
vendor-advisory
-
debian.org
/security/2013/dsa-2785
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-10/msg00002.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2013-12/msg00002.html
vendor-advisory
- code.google.com /p/chromium/issues/detail?id=237800
- googlechromereleases.blogspot.com /2013/10/stable-channel-update.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A18103
vdb-entry, signature
- code.google.com /p/chromium/issues/detail?id=294206
- code.google.com /p/chromium/issues/detail?id=284792
- code.google.com /p/chromium/issues/detail?id=274020
- code.google.com /p/chromium/issues/detail?id=264211
- code.google.com /p/chromium/issues/detail?id=276111
- code.google.com /p/chromium/issues/detail?id=265731
- code.google.com /p/chromium/issues/detail?id=288771
- code.google.com /p/chromium/issues/detail?id=254728
- code.google.com /p/chromium/issues/detail?id=294202
- code.google.com /p/chromium/issues/detail?id=288761
- code.google.com /p/chromium/issues/detail?id=246724
- code.google.com /p/chromium/issues/detail?id=266593
- code.google.com /p/chromium/issues/detail?id=299016
- code.google.com /p/chromium/issues/detail?id=260138
- code.google.com /p/chromium/issues/detail?id=279286
- code.google.com /p/chromium/issues/detail?id=277656
- code.google.com /p/chromium/issues/detail?id=294023
- code.google.com /p/chromium/issues/detail?id=257852
- code.google.com /p/chromium/issues/detail?id=269835
- code.google.com /p/chromium/issues/detail?id=267068
- code.google.com /p/chromium/issues/detail?id=293521
- code.google.com /p/chromium/issues/detail?id=285380
- code.google.com /p/chromium/issues/detail?id=278366
- code.google.com /p/chromium/issues/detail?id=289648
- code.google.com /p/chromium/issues/detail?id=265493
Sources
- CVE List CVE-2013-2923
- NVD CVE-2013-2923
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.