| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in SoftiaCom wMailServer 1.0/2.0. The affected element is an unknown function. The manipulation results in memory corruption. This vulnerability is reported as CVE-2005-2287. Moreover, an exploit is present.
Details
A vulnerability classified as critical has been found in SoftiaCom wMailServer 1.0/2.0 (Mail Server Software). Affected is an unknown part. 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 availability. CVE summarizes:
SoftiaCom wMailServer 1.0 and 2.0 allows remote attackers to cause a denial of service (application crash) via a large TCP packet with a leading space, possibly triggering a buffer overflow.
The weakness was disclosed 07/12/2005 by fRoGGz as not defined posting (Bugtraq). The advisory is shared for download at marc.theaimsgroup.com. This vulnerability is traded as CVE-2005-2287 since 07/17/2005. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are unknown but a public exploit is available.
The exploit is shared for download at exploit-db.com. It is declared as highly functional.
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 Exploit-DB (1101), SecurityFocus (BID 14213†), OSVDB (17883†) and Secunia (SA16033†). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
MetaSploit ID: wmailserver.rb
MetaSploit Name: SoftiaCom WMailserver 1.0 Buffer Overflow
MetaSploit File: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/11/2005 🔍07/12/2005 🔍
07/12/2005 🔍
07/12/2005 🔍
07/17/2005 🔍
07/18/2005 🔍
03/11/2015 🔍
03/26/2019 🔍
Sources
Advisory: marc.theaimsgroup.comResearcher: fRoGGz
Status: Not defined
CVE: CVE-2005-2287 (🔍)
GCVE (CVE): GCVE-0-2005-2287
GCVE (VulDB): GCVE-100-25812
SecurityFocus: 14213 - SoftiaCom WMailserver Remote Buffer Overflow Vulnerability
Secunia: 16033 - wMailserver Insecure Registry Permission and Denial of Service, Moderately Critical
OSVDB: 17883 - wMailserver SMTP Service Remote Overflow DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2015 23:39Updated: 03/26/2019 10:03
Changes: 03/11/2015 23:39 (65), 03/26/2019 10:03 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.