| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in W3 Amaya 11.1. This affects an unknown part. Such manipulation leads to memory corruption. This vulnerability is documented as CVE-2009-1209. Additionally, an exploit exists.
Details
A vulnerability was found in W3 Amaya 11.1. It has been rated as very critical. Affected by this issue is an unknown part. 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:
Stack-based buffer overflow in W3C Amaya Web Browser 11.1 allows remote attackers to execute arbitrary code via a script tag with a long defer attribute.
The weakness was released 04/01/2009 (Website). The advisory is shared for download at milw0rm.com. This vulnerability is handled as CVE-2009-1209 since 03/31/2009. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a public exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/25/2024).
The exploit is available at securityfocus.com. It is declared as proof-of-concept.
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 (47399), SecurityFocus (BID 34295†), Secunia (SA34531†) and Vulnerability Center (SBV-31491†). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.1
VulDB Base Score: 10.0
VulDB Temp Score: 9.1
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/15/2008 🔍03/30/2009 🔍
03/31/2009 🔍
03/31/2009 🔍
04/01/2009 🔍
04/01/2009 🔍
05/22/2011 🔍
03/17/2015 🔍
11/25/2024 🔍
Sources
Advisory: milw0rm.com⛔Status: Not defined
CVE: CVE-2009-1209 (🔍)
GCVE (CVE): GCVE-0-2009-1209
GCVE (VulDB): GCVE-100-47456
X-Force: 47399
SecurityFocus: 34295 - W3C Amaya HTML 'script' Tag Buffer Overflow Vulnerability
Secunia: 34531 - Amaya Multiple Vulnerabilities, Highly Critical
Vulnerability Center: 31491 - W3C Amaya Web Browser 11.1 Remote Arbitrary Code Execution Vulnerability via a Script Tag, High
Vupen: ADV-2009-0889
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/17/2015 23:38Updated: 11/25/2024 19:44
Changes: 03/17/2015 23:38 (47), 03/22/2017 21:49 (16), 08/09/2021 11:06 (2), 11/25/2024 19:44 (19)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.