Sylpheed 0.9.4/0.9.5/0.9.6 Error Message send_message.c format string
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Sylpheed 0.9.4/0.9.5/0.9.6 and classified as critical. Affected by this issue is some unknown functionality of the file send_message.c of the component Error Message Handler. This manipulation causes format string. The identification of this vulnerability is CVE-2003-0852. There is no exploit available.
Details
A vulnerability classified as critical was found in Sylpheed 0.9.4/0.9.5/0.9.6. Affected by this vulnerability is an unknown part of the file send_message.c of the component Error Message Handler. The manipulation with an unknown input leads to a format string vulnerability. The CWE definition for the vulnerability is CWE-134. The product uses a function that accepts a format string as an argument, but the format string originates from an external source. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Format string vulnerability in send_message.c for Sylpheed-claws 0.9.4 through 0.9.6 allows remote SMTP servers to cause a denial of service (crash) in sylpheed via format strings in an error message.
The weakness was shared 11/17/2003 by Georgi Guninski (Website). The advisory is shared at lists.grok.org.uk. This vulnerability is known as CVE-2003-0852 since 10/10/2003. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
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 (13508) and SecurityFocus (BID 8877†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
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: Format stringCWE: CWE-134 / 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
10/10/2003 🔍10/22/2003 🔍
11/17/2003 🔍
11/17/2003 🔍
08/15/2014 🔍
06/15/2018 🔍
Sources
Advisory: lists.grok.org.ukResearcher: Georgi Guninski
Status: Not defined
Confirmation: 🔍
CVE: CVE-2003-0852 (🔍)
GCVE (CVE): GCVE-0-2003-0852
GCVE (VulDB): GCVE-100-20989
X-Force: 13508
SecurityFocus: 8877
Entry
Created: 08/15/2014 16:40Updated: 06/15/2018 08:11
Changes: 08/15/2014 16:40 (46), 06/15/2018 08:11 (6)
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.