Sun Java System Calendar Server 6 service.http.commandlog.all denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Sun Java System Calendar Server 6. Affected by this issue is some unknown functionality of the file service.http.commandlog.all of the component Calendar Server. Performing a manipulation results in denial of service. This vulnerability was named CVE-2008-2749. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Sun Java System Calendar Server 6 (Calendar Software). This affects an unknown functionality of the file service.http.commandlog.all of the component Calendar Server. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
Unspecified vulnerability in cshttpd in Sun Java System Calendar Server 6 and 6.3, and Sun ONE Calendar Server 6.0, when access logging (aka service.http.commandlog.all) is enabled, allows remote attackers to cause a denial of service (daemon crash) via unspecified vectors.
The weakness was presented 06/18/2008 (Website). The advisory is shared at sunsolve.sun.com. This vulnerability is uniquely identified as CVE-2008-2749 since 06/18/2008. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
It is declared as proof-of-concept.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (43127), SecurityFocus (BID 29763†), Secunia (SA30694†) and SecurityTracker (ID 1020299†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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: 7.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 7.5
VulDB Temp Score: 6.5
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
06/13/2008 🔍06/17/2008 🔍
06/18/2008 🔍
06/18/2008 🔍
06/18/2008 🔍
03/16/2015 🔍
11/14/2017 🔍
Sources
Vendor: oracle.comAdvisory: sunsolve.sun.com⛔
Status: Confirmed
CVE: CVE-2008-2749 (🔍)
GCVE (CVE): GCVE-0-2008-2749
GCVE (VulDB): GCVE-100-42813
X-Force: 43127 - Sun Java System Calendar Server unspecified denial of service
SecurityFocus: 29763 - Sun Java System Calendar Server Denial of Service Vulnerability
Secunia: 30694
SecurityTracker: 1020299
Vupen: ADV-2008-1857
Entry
Created: 03/16/2015 17:00Updated: 11/14/2017 13:45
Changes: 03/16/2015 17:00 (52), 11/14/2017 13:45 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.