LiveActive security incident?Get immediate response
CVE Record

CVE-2010-1773: Off-by-one error in the toAlphabetic function in rendering/RenderListMarker.cpp in WebCore in WebKit before...

Off-by-one error in the toAlphabetic function in rendering/RenderListMarker.cpp in WebCore in WebKit before r59950, as used in Google Chrome before 5.0.375.70, allows remote attackers to obtain sensitive information, cause a denial of service (memory corruption and application crash), or possibly execute arbitrary code via vectors related to list markers for HTML lists, aka rdar problem 8009118.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2010-1773 is an old WebKit browser-engine memory corruption flaw tied to HTML list markers. A malicious web page could crash the application, expose sensitive information, or possibly run code. Business risk is mainly in legacy browsers, embedded WebKit components, and unsupported systems that still carry WebKit before r59950 or Chrome before 5.0.375.70. Exposure is most likely in legacy Google Chrome, WebKit-based applications, or older Linux distribution packages referenced by vendor advisories. Current managed endpoints are unlikely to be exposed unless they run unsupported browsers, embedded browser controls, kiosk software, or unmaintained WebKit packages. Treat this as high priority only where legacy WebKit or Chrome remains in production. For modern managed fleets, priority should be verification-driven: confirm absence of old browser engines, then document closure. Unsupported embedded browser components deserve special attention because they often escape normal patch inventories. Mitigation focus: Update WebKit-based software to a build including r59950 or later.; Update Google Chrome beyond 5.0.375.70 where legacy Chrome exists.; Apply relevant distribution security updates from Ubuntu, Fedora, Mandriva, or SUSE advisories..

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2010-1773 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.