CVE-2013-2909
Use-after-free vulnerability in Blink, as used in Google Chrome before ...
Overview
Description
Use-after-free vulnerability in Blink, as used in Google Chrome before 30.0.1599.66, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to inline-block rendering for bidirectional Unicode text in an element isolated from its siblings.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Weakness: CWE-399
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 2 fixes
openSUSE 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Tumbleweed | ungoogled-chromium +1 | 113.0.5672.92-1.1 | openSUSE-SU-2024:12948-1 |
| Tumbleweed | chromedriver +1 | 55.0.2883.75-3.1 | openSUSE-SU-2024:10171-1 |
References
- googlechromereleases.blogspot.com http://googlechromereleases.blogspot.com/2013/10/stable-channel-update.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2013-10/msg00002.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.html
- lists.opensuse.org http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- support.apple.com http://support.apple.com/kb/HT6162
- support.apple.com http://support.apple.com/kb/HT6163
- www.debian.org http://www.debian.org/security/2013/dsa-2785
- code.google.com https://code.google.com/p/chromium/issues/detail?id=265838
- code.google.com https://code.google.com/p/chromium/issues/detail?id=279277
- oval.cisecurity.org https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19012
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.