CVE-2010-3567 Memory corruption in n/a

Critical 10.0 Published Updated

Remote attackers can execute arbitrary code or cause denial of service via memory corruption in Java's 2D text rendering component.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2010-3567?

CVE-2010-3567 is a critical memory corruption vulnerability in Sun Jdk, published on 19 Oct 2010. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

Unspecified vulnerability in the 2D component in Oracle Java SE and Java for Business 6 Update 21, and 5.0 Update 25 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the October 2010 CPU. Oracle has not commented on claims from a reliable downstream vendor that this is related to a calculation error in right-to-left text character counts for the ICU OpenType font rendering implementation, which triggers an out-of-bounds memory access.

Which versions are affected by CVE-2010-3567?

It affects 2 products.

Products include Sun Jdk, Sun Jre.

How do I fix CVE-2010-3567?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2010-3567 being exploited?

There is no known exploitation of CVE-2010-3567 in the wild and no public exploit code.

All Sun Jdk vulnerabilities

Sources

Also known as GHSA-4mq8-fgx6-fqpv.

Is CVE-2010-3567 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free