LiveActive security incident?Get immediate response
CVE Record

CVE-2010-3567: Unspecified vulnerability in the 2D component in Oracle Java SE and Java for Business 6 Update 21, and 5.0...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2010-3567 is an old Java 2D flaw in Oracle Java SE and Java for Business 6 Update 21 and 5.0 Update 25. A remote attacker could affect confidentiality, integrity, and availability through unspecified vectors. The business risk is mainly legacy Java runtimes or enterprise products that bundled vulnerable Java. Exposure is most likely in obsolete Java 5 or Java 6 deployments, browser-plugin-era clients, servers, or vendor appliances that embedded affected Java builds. Modern environments are unlikely exposed unless legacy Java remains installed or bundled. Treat this as a legacy technology cleanup issue with high potential impact if exposed. Prioritize environments where old Java is internet-reachable, user-facing, or bundled inside still-operated enterprise products. Mitigation focus: Inventory Java SE, Java for Business, OpenJDK, and bundled Java runtimes.; Apply Oracle October 2010 CPU or downstream vendor Java updates where applicable.; Check Avaya, HP, Red Hat, Ubuntu, Gentoo, and VMware guidance for bundled exposure..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2010-3567 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.