Google Chrome before 24.0.1312.52 does not properly maintain database metadata, which allows remote attackers to bypass intended file-acces…

published 2013-01-15 13y ago modified 2026-06-16 4mo ago also EUVD-2013-0840

cvss: 6.4; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits: 0; none known

Google Chrome before 24.0.1312.52 does not properly maintain database metadata, which allows remote attackers to bypass intended file-access restrictions via unspecified vectors.

Patch / fix

fixed in 1

google chrome 24.0.1312.52

Is CVE-2013-0829 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

Exploit prediction

0.96% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:P/I:P/A:N

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls

Technology feeds

Google Chrome rss critical rss

References

Sources

CVE List CVE-2013-0829
NVD CVE-2013-0829

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.