Skip to content
Fencer Intel
high 7.5

CVE-2014-1713 json

Use-after-free vulnerability in the AttributeSetter function in bindings/templates/attributes.cpp in the bindings in Blink, as used in Goog…

published 12y ago modified 4mo ago also EUVD-2014-1787

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

Summary

Use-after-free vulnerability in the AttributeSetter function in bindings/templates/attributes.cpp in the bindings in Blink, as used in Google Chrome before 33.0.1750.152 on OS X and Linux and before 33.0.1750.154 on Windows, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving the document.location value.

Patch / fix

  • google chrome 33.0.1750.152, 33.0.1750.154
  • 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-2014-1713 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-2014-1713 updated cvss 5.1

webkitgtk: use-after-free in the AttributeSetter function (WSA-2015-0001)

  • Red Hat Enterprise Linux 6 webkitgtk Red Hat Enterprise Linux 7 webkitgtk3, libwebkit2gtk
    affected: no fix planned “Will not fix”

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

2.36% 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
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.