Skip to content
Fencer Vulns
medium 4.3

CVE-2008-6995 json

Integer underflow in net/base/escape.cc in chrome.dll in Google Chrome 0.2.149.27 allows remote attackers to cause a denial of service (bro…

published 2009-08-18 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-6954

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.8%
EPSS 4.8% chance of exploitation in 30 days, percentile 92%
public exploits
1
Exploit-DB

Summary

Integer underflow in net/base/escape.cc in chrome.dll in Google Chrome 0.2.149.27 allows remote attackers to cause a denial of service (browser crash) via a URI with an invalid handler followed by a "%" (percent) character, which triggers a buffer over-read, as demonstrated using an "about:%" URI.

Timeline

  1. First public exploit (EDB-6353)
  2. Published

Exploit prediction

4.80% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-6353 Google Chrome 0.2.149.27 - Denial of Service dos, 2008-09-03
  • osvdb.org http://osvdb.org/47908 referenced PoC, tagged "exploit" by a source, unverified
  • evilfingers.com https://www.evilfingers.com/advisory/Google_Chrome_Browser_0.2.149.27_in_chrome_dll.php referenced PoC, tagged "exploit" by a source, unverified
  • archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2008-09/0028.html referenced PoC, tagged "exploit" by a source, unverified
  • src.chromium.org http://src.chromium.org/viewvc/chrome/branches/chrome_official_branch/src/net/base/escape.cc?r1=1757&r2=1760&pathrev=1760 referenced PoC, tagged "exploit" by a source, unverified
  • evilfingers.com http://evilfingers.com/advisory/google_chrome_poc.php referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/30983 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns 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.