Analyst readout for executives and security teams
Plain-English summary
This is an old Google Chrome vulnerability fixed in Chrome 10.0.648.127. A malicious remote page could trigger incorrect box layout handling, causing denial of service or possibly other unspecified effects tied to a stale node. The public record does not provide CVSS, exploit status, or detailed impact.
Executive priority
Treat this as a legacy browser hygiene issue unless old Chrome versions remain in production. There is no supplied evidence of active exploitation, but browser vulnerabilities can become business risk when unsupported software persists on endpoints or kiosks.
Technical view
Chrome before 10.0.648.127 improperly performed box layout. The CVE says unknown remote vectors could lead to a stale node condition, with denial of service or unspecified other impact. No CWE, CVSS vector, proof-of-concept detail, or precise affected platform list is provided in the supplied sources.
Likely exposure
Exposure is most likely limited to unmanaged, embedded, or legacy systems still running Chrome versions earlier than 10.0.648.127. Modern supported Chrome deployments are unlikely to be exposed, but the bundle does not provide platform-specific affected CPEs.
Exploitation context
The supplied bundle does not show CISA KEV listing or any cited evidence of active exploitation. The vulnerability is remotely reachable through unknown vectors, but public detail here is too limited to assess exploit maturity or reliability.
Researcher notes
Key gaps are the unknown attack vector, missing CVSS, absent CWE mapping, and unspecified non-DoS impact. The Chromium issue and vendor release reference are important primary leads, but the supplied bundle does not include enough detail to characterize root cause or exploitability.
Mitigation direction
- Upgrade Chrome to version 10.0.648.127 or later.
- Remove unsupported legacy Chrome builds from enterprise systems.
- Check vendor release notes for any additional guidance.
- Prioritize remediation on kiosks, VDI images, and embedded browser deployments.
Validation and detection
- Inventory Chrome versions across managed and unmanaged endpoints.
- Flag any Chrome version earlier than 10.0.648.127.
- Review vulnerability scanner detections for OVAL definition oval:org.mitre.oval:def:14370.
- Confirm legacy images and golden builds no longer contain affected Chrome versions.
Public sources used
Based on public source material and reviewed before publication.
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-2011-1189 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- oval:org.mitre.oval:def:14370CVE reference · vdb-entry, signature
- 46785CVE reference · vdb-entry, x_refsource_BID
- http://googlechromereleases.blogspot.com/2011/03/chrome-stable-release.htmlCVE reference · x_refsource_CONFIRM
- google-box-layouts-dos(65953)CVE reference · vdb-entry, x_refsource_XF
- http://code.google.com/p/chromium/issues/detail?id=70027CVE reference · x_refsource_CONFIRM
- ADV-2011-0628CVE reference · vdb-entry, x_refsource_VUPEN
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
