Skip to content
Fencer Intel
high 7.5

CVE-2013-2919 json

Google V8, as used in Google Chrome before 30.0.1599.66, allows remote attackers to cause a denial of service (memory corruption) or possib…

published 13y ago modified 4mo ago also EUVD-2013-2858

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

Google V8, as used in Google Chrome before 30.0.1599.66, allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.

Patch / fix

  • 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-2919 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 Fencer

Vendor 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-2919 updated cvss 6.8

v8: remote denial of service via memory corruption

  • Red Hat OpenShift Enterprise 1 ruby193-v8 Red Hat OpenStack Platform 3 v8, ruby193-v8 Red Hat Satellite 6 v8 Red Hat Software Collections v8314-v8 Red Hat Subscription Asset Manager v8, ruby193-v8
    not 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

1.85% chance of exploitation in the next 30 days, higher than 79% 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-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

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.