| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Sun Wireless Toolkit 2.5.2. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2008-3551. There is no available exploit.
Details
A vulnerability was found in Sun Wireless Toolkit 2.5.2. It has been classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Multiple unspecified vulnerabilities in Sun Java Platform Micro Edition (aka Java ME, J2ME, or mobile Java), as distributed in Sun Wireless Toolkit 2.5.2, allow remote attackers to execute arbitrary code via unknown vectors. NOTE: as of 20080807, the only disclosure is a vague pre-advisory with no actionable information. However, because it is from a company led by a well-known researcher, it is being assigned a CVE identifier for tracking purposes.
The weakness was presented 08/08/2008 with Security Explorations (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2008-3551 since 08/08/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 11/21/2017). It is expected to see the exploit prices for this product decreasing in the near future.
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 (44478) and SecurityFocus (BID 30591†). See VDB-43595 and VDB-43594 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Support
- end of life (old version)
Website
- Vendor: https://www.oracle.com/sun/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 8.8
VulDB Base Score: 10.0
VulDB Temp Score: 8.8
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: Unproven
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
08/07/2008 🔍08/08/2008 🔍
08/08/2008 🔍
08/08/2008 🔍
03/17/2015 🔍
11/21/2017 🔍
Sources
Vendor: oracle.comAdvisory: securityfocus.com⛔
Organization: Security Explorations
Status: Not defined
CVE: CVE-2008-3551 (🔍)
GCVE (CVE): GCVE-0-2008-3551
GCVE (VulDB): GCVE-100-43593
X-Force: 44478 - Sun Java Platform Micro Edition unspecified code execution
SecurityFocus: 30591 - Sun Java Micro Edition (ME) Multiple Unspecified Security-Bypass Vulnerabilities
See also: 🔍
Entry
Created: 03/17/2015 12:19Updated: 11/21/2017 15:52
Changes: 03/17/2015 12:19 (50), 11/21/2017 15:52 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.