Mozilla SeaMonkey 1.1.7 denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.8$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Mozilla SeaMonkey 1.1.7. This affects an unknown function. Performing a manipulation results in denial of service. This vulnerability is reported as CVE-2008-0592. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Mozilla SeaMonkey 1.1.7 (Web Browser). This affects some unknown functionality. 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:

Mozilla Firefox before 2.0.0.12 and SeaMonkey before 1.1.8 allows user-assisted remote attackers to cause a denial of service via a plain .txt file with a "Content-Disposition: attachment" and an invalid "Content-Type: plain/text," which prevents Firefox from rendering future plain text files within the browser.

The bug was discovered 02/07/2008. The weakness was disclosed 02/08/2008 by Gerry Eisenhaur with Martijn Wargers as Bug 387258 as confirmed bug report (Bugzilla). The advisory is shared at bugzilla.mozilla.org. This vulnerability is uniquely identified as CVE-2008-0592 since 02/05/2008. 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.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 30220 (CentOS 4 / 5 : firefox (CESA-2008:0103)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165669 (SUSE Enterprise Linux Security Update Mozilla Firefox and Seamonkey (SUSE-SA:2008:008)).

Upgrading to version 1.1.7 eliminates this vulnerability. A possible mitigation has been published 1 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (40384), Tenable (30220), SecurityFocus (BID 27683†), OSVDB (41225†) and Secunia (SA28754†). The entries VDB-3567, VDB-3585, VDB-3584 and VDB-3583 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 4.8

VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Denial of service
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 30220
Nessus Name: CentOS 4 / 5 : firefox (CESA-2008:0103)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 60363
OpenVAS Name: Debian Security Advisory DSA 1484-1 (xulrunner)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: SeaMonkey 1.1.7

Timelineinfo

02/05/2008 🔍
02/07/2008 +2 days 🔍
02/07/2008 +0 days 🔍
02/08/2008 +1 days 🔍
02/08/2008 +0 days 🔍
02/08/2008 +0 days 🔍
02/08/2008 +0 days 🔍
02/09/2008 +1 days 🔍
02/10/2008 +1 days 🔍
02/11/2008 +1 days 🔍
03/16/2015 +2590 days 🔍
08/04/2019 +1602 days 🔍

Sourcesinfo

Vendor: mozilla.org

Advisory: Bug 387258
Researcher: Gerry Eisenhaur
Organization: Martijn Wargers
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2008-0592 (🔍)
GCVE (CVE): GCVE-0-2008-0592
GCVE (VulDB): GCVE-100-40917

OVAL: 🔍

X-Force: 40384
SecurityFocus: 27683 - Mozilla Thunderbird/Seamonkey/Firefox 2.0.0.11 Multiple Remote Vulnerabilities
Secunia: 28754
OSVDB: 41225 - CVE-2008-0592 - Mozilla - Firefox And SeaMonkey - Denial-Of-Service Issue
SecurityTracker: 1019340
Vulnerability Center: 17559 - Mozilla Firefox < 2.0.0.12 and SeaMonkey < 1.1.8 Remote DoS via a Plain .txt File, Medium
Vupen: ADV-2008-0453

See also: 🔍

Entryinfo

Created: 03/16/2015 13:43
Updated: 08/04/2019 17:05
Changes: 03/16/2015 13:43 (80), 08/04/2019 17:05 (12)
Complete: 🔍
Cache ID: 216:7AA:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!