Dovecot up to 2.2.36.2/2.3.5.0 Indexer-Worker Process memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Dovecot up to 2.2.36.2/2.3.5.0 and classified as critical. This vulnerability affects unknown code of the component Indexer-Worker Process. Performing a manipulation results in memory corruption. This vulnerability is reported as CVE-2019-7524. The attack requires a local approach. No exploit exists. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in Dovecot up to 2.2.36.2/2.3.5.0 (Mail Server Software). This affects an unknown part of the component Indexer-Worker Process. 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 confidentiality, integrity, and availability. The summary by CVE is:
In Dovecot before 2.2.36.3 and 2.3.x before 2.3.5.1, a local attacker can cause a buffer overflow in the indexer-worker process, which can be used to elevate to root. This occurs because of missing checks in the fts and pop3-uidl components.
The bug was discovered 03/28/2019. The weakness was disclosed 03/28/2019 by Aki Tuomi (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2019-7524 since 02/06/2019. An attack has to be approached locally. A authentication is necessary for exploitation. Neither technical details nor an exploit are publicly available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 172203 (SUSE Enterprise Linux Security Update for dovecot22 (SUSE-SU-2019:0900-1)).
Upgrading to version 2.2.36.3 or 2.3.5.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 107672†). The entry VDB-132543 is pretty similar. 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: 8.1VulDB Meta Temp Score: 8.0
VulDB Base Score: 7.8
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.8
NVD Vector: 🔍
CNA Base Score: 8.8
CNA Vector (MITRE): 🔍
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: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Dovecot 2.2.36.3/2.3.5.1
Timeline
02/06/2019 🔍03/28/2019 🔍
03/28/2019 🔍
03/29/2019 🔍
04/02/2019 🔍
08/17/2023 🔍
Sources
Advisory: USN-3928-1Researcher: Aki Tuomi
Status: Confirmed
CVE: CVE-2019-7524 (🔍)
GCVE (CVE): GCVE-0-2019-7524
GCVE (VulDB): GCVE-100-132597
SecurityFocus: 107672 - Dovecot CVE-2019-7524 Stack Buffer Overflow Vulnerability
See also: 🔍
Entry
Created: 03/29/2019 06:47Updated: 08/17/2023 15:35
Changes: 03/29/2019 06:47 (61), 05/22/2020 18:10 (4), 08/17/2023 15:30 (4), 08/17/2023 15:35 (12)
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.