CVE-2013-2931
First published: Wed Nov 13 2013(Updated: )
Multiple unspecified vulnerabilities in Google Chrome before 31.0.1650.48 allow attackers to execute arbitrary code or possibly have other impact via unknown vectors.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <=31.0.1650.47 | |
| Google Chrome (Trace Event) | =31.0.1650.0 | |
| Google Chrome (Trace Event) | =31.0.1650.2 | |
| Google Chrome (Trace Event) | =31.0.1650.3 | |
| Google Chrome (Trace Event) | =31.0.1650.4 | |
| Google Chrome (Trace Event) | =31.0.1650.5 | |
| Google Chrome (Trace Event) | =31.0.1650.6 | |
| Google Chrome (Trace Event) | =31.0.1650.7 | |
| Google Chrome (Trace Event) | =31.0.1650.8 | |
| Google Chrome (Trace Event) | =31.0.1650.9 | |
| Google Chrome (Trace Event) | =31.0.1650.10 | |
| Google Chrome (Trace Event) | =31.0.1650.11 | |
| Google Chrome (Trace Event) | =31.0.1650.12 | |
| Google Chrome (Trace Event) | =31.0.1650.13 | |
| Google Chrome (Trace Event) | =31.0.1650.14 | |
| Google Chrome (Trace Event) | =31.0.1650.15 | |
| Google Chrome (Trace Event) | =31.0.1650.16 | |
| Google Chrome (Trace Event) | =31.0.1650.17 | |
| Google Chrome (Trace Event) | =31.0.1650.18 | |
| Google Chrome (Trace Event) | =31.0.1650.19 | |
| Google Chrome (Trace Event) | =31.0.1650.20 | |
| Google Chrome (Trace Event) | =31.0.1650.22 | |
| Google Chrome (Trace Event) | =31.0.1650.23 | |
| Google Chrome (Trace Event) | =31.0.1650.25 | |
| Google Chrome (Trace Event) | =31.0.1650.26 | |
| Google Chrome (Trace Event) | =31.0.1650.27 | |
| Google Chrome (Trace Event) | =31.0.1650.28 | |
| Google Chrome (Trace Event) | =31.0.1650.29 | |
| Google Chrome (Trace Event) | =31.0.1650.30 | |
| Google Chrome (Trace Event) | =31.0.1650.31 | |
| Google Chrome (Trace Event) | =31.0.1650.32 | |
| Google Chrome (Trace Event) | =31.0.1650.33 | |
| Google Chrome (Trace Event) | =31.0.1650.34 | |
| Google Chrome (Trace Event) | =31.0.1650.35 | |
| Google Chrome (Trace Event) | =31.0.1650.36 | |
| Google Chrome (Trace Event) | =31.0.1650.37 | |
| Google Chrome (Trace Event) | =31.0.1650.38 | |
| Google Chrome (Trace Event) | =31.0.1650.39 | |
| Google Chrome (Trace Event) | =31.0.1650.41 | |
| Google Chrome (Trace Event) | =31.0.1650.42 | |
| Google Chrome (Trace Event) | =31.0.1650.43 | |
| Google Chrome (Trace Event) | =31.0.1650.44 | |
| Google Chrome (Trace Event) | =31.0.1650.45 | |
| Google Chrome (Trace Event) | =31.0.1650.46 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://googlechromereleases.blogspot.com/2013/11/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00025.html
- http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00026.html
- http://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- http://www.debian.org/security/2013/dsa-2799
- https://code.google.com/p/chromium/issues/detail?id=258723
- https://code.google.com/p/chromium/issues/detail?id=263255
- https://code.google.com/p/chromium/issues/detail?id=264574
- https://code.google.com/p/chromium/issues/detail?id=271235
- https://code.google.com/p/chromium/issues/detail?id=282738
- https://code.google.com/p/chromium/issues/detail?id=285578
- https://code.google.com/p/chromium/issues/detail?id=286368
- https://code.google.com/p/chromium/issues/detail?id=296276
- https://code.google.com/p/chromium/issues/detail?id=296804
- https://code.google.com/p/chromium/issues/detail?id=297556
- https://code.google.com/p/chromium/issues/detail?id=299835
- https://code.google.com/p/chromium/issues/detail?id=299993
- https://code.google.com/p/chromium/issues/detail?id=302810
- https://code.google.com/p/chromium/issues/detail?id=303232
- https://code.google.com/p/chromium/issues/detail?id=304226
- https://code.google.com/p/chromium/issues/detail?id=306255
- https://code.google.com/p/chromium/issues/detail?id=314225
- https://code.google.com/p/chromium/issues/detail?id=315823
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19183
Frequently Asked Questions
What is the severity of CVE-2013-2931?
CVE-2013-2931 is considered a high severity vulnerability that allows attackers to execute arbitrary code.
How do I fix CVE-2013-2931?
To fix CVE-2013-2931, users should update Google Chrome to version 31.0.1650.48 or later.
What versions of Google Chrome are affected by CVE-2013-2931?
CVE-2013-2931 affects all versions of Google Chrome prior to 31.0.1650.48.
What types of attacks can CVE-2013-2931 enable?
CVE-2013-2931 can enable attacks that execute arbitrary code through unspecified vectors.
Is CVE-2013-2931 still relevant today?
While CVE-2013-2931 was significant at the time of discovery, it is considered less relevant today due to the availability of updated browser versions.
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/last-modified-date
- agent/references
- agent/author
- agent/severity
- agent/tags
- agent/description
- agent/event
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/31.0.1650.47
- version/google chrome (trace event)/31.0.1650.0
- version/google chrome (trace event)/31.0.1650.2
- version/google chrome (trace event)/31.0.1650.3
- version/google chrome (trace event)/31.0.1650.4
- version/google chrome (trace event)/31.0.1650.5
- version/google chrome (trace event)/31.0.1650.6
- version/google chrome (trace event)/31.0.1650.7
- version/google chrome (trace event)/31.0.1650.8
- version/google chrome (trace event)/31.0.1650.9
- version/google chrome (trace event)/31.0.1650.10
- version/google chrome (trace event)/31.0.1650.11
- version/google chrome (trace event)/31.0.1650.12
- version/google chrome (trace event)/31.0.1650.13
- version/google chrome (trace event)/31.0.1650.14
- version/google chrome (trace event)/31.0.1650.15
- version/google chrome (trace event)/31.0.1650.16
- version/google chrome (trace event)/31.0.1650.17
- version/google chrome (trace event)/31.0.1650.18
- version/google chrome (trace event)/31.0.1650.19
- version/google chrome (trace event)/31.0.1650.20
- version/google chrome (trace event)/31.0.1650.22
- version/google chrome (trace event)/31.0.1650.23
- version/google chrome (trace event)/31.0.1650.25
- version/google chrome (trace event)/31.0.1650.26
- version/google chrome (trace event)/31.0.1650.27
- version/google chrome (trace event)/31.0.1650.28
- version/google chrome (trace event)/31.0.1650.29
- version/google chrome (trace event)/31.0.1650.30
- version/google chrome (trace event)/31.0.1650.31
- version/google chrome (trace event)/31.0.1650.32
- version/google chrome (trace event)/31.0.1650.33
- version/google chrome (trace event)/31.0.1650.34
- version/google chrome (trace event)/31.0.1650.35
- version/google chrome (trace event)/31.0.1650.36
- version/google chrome (trace event)/31.0.1650.37
- version/google chrome (trace event)/31.0.1650.38
- version/google chrome (trace event)/31.0.1650.39
- version/google chrome (trace event)/31.0.1650.41
- version/google chrome (trace event)/31.0.1650.42
- version/google chrome (trace event)/31.0.1650.43
- version/google chrome (trace event)/31.0.1650.44
- version/google chrome (trace event)/31.0.1650.45
- version/google chrome (trace event)/31.0.1650.46