| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Dovecot up to 1.2.10. It has been rated as problematic. This issue affects some unknown processing. Performing a manipulation results in resource management. This vulnerability is reported as CVE-2010-0745. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability was found in Dovecot up to 1.2.10 (Mail Server Software). It has been classified as problematic. This affects an unknown function. The manipulation with an unknown input leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on availability. The summary by CVE is:
Unspecified vulnerability in Dovecot 1.2.x before 1.2.11 allows remote attackers to cause a denial of service (CPU consumption) via long headers in an e-mail message.
The weakness was disclosed 05/20/2010 (Website). The advisory is shared at dovecot.org. This vulnerability is uniquely identified as CVE-2010-0745. The exploitability is told to be easy. 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.
The vulnerability scanner Nessus provides a plugin with the ID 46178 (openSUSE Security Update : dovecot12 (openSUSE-SU-2010:0175-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165222 (SUSE Security Update for Multiple Packages (SUSE-SR:2010:011)).
Upgrading to version 1.2.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (46178) and Vulnerability Center (SBV-25644†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
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.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Resource managementCWE: CWE-399 / CWE-404
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 |
Nessus ID: 46178
Nessus Name: openSUSE Security Update : dovecot12 (openSUSE-SU-2010:0175-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
OpenVAS ID: 830949
OpenVAS Name: Mandriva Update for iptables MDVA-2010:104 (iptables)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Dovecot 1.2.4
Timeline
02/26/2010 🔍04/26/2010 🔍
04/29/2010 🔍
05/06/2010 🔍
05/20/2010 🔍
05/20/2010 🔍
03/19/2015 🔍
05/23/2025 🔍
Sources
Advisory: dovecot.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2010-0745 (🔍)
GCVE (CVE): GCVE-0-2010-0745
GCVE (VulDB): GCVE-100-53277
Vulnerability Center: 25644 - Dovecot before 1.2.11 Remote DoS Vulnerability, High
Entry
Created: 03/19/2015 12:22Updated: 05/23/2025 00:22
Changes: 03/19/2015 12:22 (56), 02/24/2017 09:43 (6), 09/14/2021 01:46 (4), 09/14/2021 01:54 (1), 05/23/2025 00:22 (18)
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.