W3C Amaya Web Browser 11.0.1 CheckUniqueName memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 10.0 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in W3C Amaya Web Browser 11.0.1. This impacts the function CheckUniqueName. Such manipulation leads to memory corruption.
This vulnerability is traded as CVE-2008-6005. There is no exploit available.
Details
A vulnerability, which was classified as very critical, has been found in W3C Amaya Web Browser 11.0.1 (Web Browser). Affected by this issue is the function CheckUniqueName. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Multiple buffer overflows in the CheckUniqueName function in W3C Amaya Web Browser 10.0.1, and possibly other versions including 11.0.1, might allow remote attackers to execute arbitrary code via "duplicated" attribute value inputs.
The weakness was shared 01/28/2009 by Nico Golde (Website). The advisory is available at securityfocus.com. This vulnerability is handled as CVE-2008-6005 since 01/28/2009. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 03/22/2017).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (48399), SecurityFocus (BID 33736†) and Vulnerability Center (SBV-31493†). The entry VDB-46155 is related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 10.0
VulDB Base Score: 10.0
VulDB Temp Score: 10.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/23/2008 🔍01/28/2009 🔍
01/28/2009 🔍
01/28/2009 🔍
01/28/2009 🔍
05/22/2011 🔍
03/17/2015 🔍
03/22/2017 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Nico Golde
Status: Not defined
Confirmation: 🔍
CVE: CVE-2008-6005 (🔍)
GCVE (CVE): GCVE-0-2008-6005
GCVE (VulDB): GCVE-100-46154
X-Force: 48399
SecurityFocus: 33736 - W3C Amaya 'CheckUniqueName()' Multiple Stack Based Buffer Overflow Vulnerabilities
Vulnerability Center: 31493 - W3C Amaya Remote Arbitrary Code Execution Vulnerability via \, High
See also: 🔍
Entry
Created: 03/17/2015 16:11Updated: 03/22/2017 21:49
Changes: 03/17/2015 16:11 (48), 03/22/2017 21:49 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.