Cerulean Studios Trillian 3.1.0.120 Rich Text Format denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Cerulean Studios Trillian 3.1.0.120. It has been rated as problematic. This vulnerability affects unknown code of the component Rich Text Format. Performing a manipulation results in denial of service. This vulnerability is identified as CVE-2006-0543. Additionally, an exploit exists.
Details
A vulnerability was found in Cerulean Studios Trillian 3.1.0.120 (Messaging Software). It has been classified as problematic. This affects an unknown function of the component Rich Text Format. 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:
Cerulean Trillian 3.1.0.120 allows remote attackers to cause a denial of service (client crash) via an AIM message containing the Mac encoded Rich Text Format (RTF) escape sequences (1) \ d1, (2) \ d2, (3) \ d3, (4) \ d4, and (5) \ d5. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
The bug was discovered 09/26/2005. The weakness was released 02/01/2006 by Sullo (Website). The advisory is shared at osvdb.org. This vulnerability is uniquely identified as CVE-2006-0543 since 02/04/2006. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but an exploit is available.
After 23 hours, there has been an exploit disclosed. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 128 days. During that time the estimated underground price was around $0-$5k.
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 vulnerability database at OSVDB (22877†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
09/26/2005 🔍02/01/2006 🔍
02/01/2006 🔍
02/01/2006 🔍
02/03/2006 🔍
02/04/2006 🔍
03/12/2015 🔍
07/18/2018 🔍
Sources
Advisory: osvdb.org⛔Researcher: Sullo
Status: Not defined
CVE: CVE-2006-0543 (🔍)
GCVE (CVE): GCVE-0-2006-0543
GCVE (VulDB): GCVE-100-28581
OSVDB: 22877 - Trillian RTF Character Remote DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/12/2015 11:11Updated: 07/18/2018 09:44
Changes: 03/12/2015 11:11 (49), 07/18/2018 09:44 (7)
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.