How severe is CVE-2010-1731?

CVE-2010-1731 has a CVSS 2.0 base score of 4.3, rated medium severity.

Is CVE-2010-1731 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2010-1731?

CVE-2010-1731 affects Google Chrome. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2010-1731?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2010-1731 published?

CVE-2010-1731 was published on 2010-05-06 and last updated on 2026-06-16.

CVE-2010-1731

CVE-2010-1731 is a medium-severity vulnerability in Google Chrome with a CVSS 2.0 base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.3)
EPSS exploit prediction: 1% (51st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Google Chrome
Published: 2010-05-06
Last modified: 2026-06-16

Description

Google Chrome on the HTC Hero allows remote attackers to cause a denial of service (application crash) via JavaScript that writes <marquee> sequences in an infinite loop.

Frequently asked questions

What is CVE-2010-1731?: Google Chrome on the HTC Hero allows remote attackers to cause a denial of service (application crash) via JavaScript that writes <marquee> sequences in an infinite loop.
How severe is CVE-2010-1731?: CVE-2010-1731 has a CVSS 2.0 base score of 4.3, rated medium severity.
Is CVE-2010-1731 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-1731?: CVE-2010-1731 affects Google Chrome. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2010-1731?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2010-1731 published?: CVE-2010-1731 was published on 2010-05-06 and last updated on 2026-06-16.

References

http://h.ackack.net/?p=258

Affected products (1)

cpe:2.3:a:google:chrome:-:*:*:*:*:*:*:*

More vulnerabilities in Google Chrome

CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
CVE-2015-8548 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow…
CVE-2015-6791 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.80 allow attackers to cause a denial of service…
CVE-2015-6788 — Critical (CVSS 10.0): The ObjectBackedNativeHandler class in extensions/renderer/object_backed_native_handler.cc in the extensions subsystem…
CVE-2015-8480 — Critical (CVSS 10.0): The VideoFramePool::PoolImpl::CreateFrame function in media/base/video_frame_pool.cc in Google Chrome before…
CVE-2015-6787 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.73 allow attackers to cause a denial of service…

All CVEs affecting Google Chrome →