Approved changes feed: RSS · Atom

cpe:2.3:a:google:chrome:0.1.42.2:*:*:*:*:*:*:*

part: a version: 0.1.42.2 update: *

VendorGoogle (f181d1eb-7269-5bae-b76e-e66ceb214562)
ProductChrome (7761a6b4-a4d4-5c42-a32a-f1a892237802)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2010-1851 vulnerable 2026-06-08 04:54:10.724924 Details available
Google Chrome, when the Invisible Hand extension is enabled, uses cookies during background HTTP requests in a possibly unexpected manner, which might allow remote web servers to identify specific persons and their product searches via HTTP request logging, related to a "cross-site data leakage" issue.
Published: 2010-05-07T17:43:00.000Z
Updated: 2024-08-07T01:35:53.636Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2010-1236 vulnerable 2026-06-08 04:54:06.794844 Details available
The protocolIs function in platform/KURLGoogle.cpp in WebCore in WebKit before r55822, as used in Google Chrome before 4.1.249.1036 and Flock Browser 3.x before 3.0.0.4112, does not properly handle whitespace at the beginning of a URL, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted javascript: URL, as demonstrated by a \x00javascript:alert sequence.
Published: 2010-04-01T22:00:00.000Z
Updated: 2024-08-07T01:14:06.681Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2010-1234 vulnerable 2026-06-08 04:54:06.671783 Details available
Unspecified vulnerability in Google Chrome before 4.1.249.1036 allows remote attackers to truncate the URL shown in the HTTP Basic Authentication dialog via unknown vectors.
Published: 2010-04-01T22:00:00.000Z
Updated: 2024-08-07T01:14:06.679Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2008-7294 vulnerable 2026-06-08 04:51:06.697177 Details available
Google Chrome before 4.0.211.0 cannot properly restrict modifications to cookies established in HTTPS sessions, which allows man-in-the-middle attackers to overwrite or delete arbitrary cookies via a Set-Cookie header in an HTTP response, related to lack of the HTTP Strict Transport Security (HSTS) includeSubDomains feature, aka a "cookie forcing" issue.
Published: 2011-08-09T19:00:00.000Z
Updated: 2024-09-17T01:46:02.151Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.