Atrium Mercur Messaging 2005 Sp4 MCRIMAP4.EXE bytes memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
9.4 | $0-$5k | 0.00 |
A vulnerability, which was classified as very critical, was found in Atrium Mercur Messaging 2005 Sp4. Affected is an unknown code of the file MCRIMAP4.EXE. The manipulation of the argument bytes
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. CVE summarizes:
Stack-based buffer overflow in Atrium MERCUR IMAPD allows remote attackers to have an unknown impact via a certain SUBSCRIBE command.
The weakness was published 03/20/2007 by Winny Thomas (Website). The advisory is shared for download at immunityinc.com. This vulnerability is traded as CVE-2007-1579 since 03/21/2007. 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 and a public exploit are known. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/06/2019).
A public exploit has been developed by Winny Thomas and been published before and not just after the advisory. The exploit is shared for download at saintcorporation.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Attack attempts may be identified with Snort ID 3074.
The vulnerability is also documented in the databases at X-Force (33216) and Exploit-DB (3537).
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.4
VulDB Base Score: 10.0
VulDB Temp Score: 9.4
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: 🔍
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Winny Thomas
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Saint ID: exploit_info/mercur_imap_subscribe
Saint Name: MERCUR imapd SUBSCRIBE command buffer overflow
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Snort ID: 3074
Snort Message: PROTOCOL-IMAP SUBSCRIBE overflow attempt
Snort Class: 🔍
Timeline
03/20/2007 🔍03/20/2007 🔍
03/20/2007 🔍
03/21/2007 🔍
03/21/2007 🔍
03/21/2007 🔍
03/26/2007 🔍
03/26/2007 🔍
03/13/2015 🔍
04/06/2019 🔍
Sources
Advisory: immunityinc.comResearcher: Winny Thomas
Status: Confirmed
CVE: CVE-2007-1579 (🔍)
X-Force: 33216 - Atrium MERCUR Messaging SUBSCRIBE command buffer overflow
SecurityFocus: 23050 - Atrium Mercur IMap Subscribe Stack Buffer Overflow Vulnerability
Secunia: 24619 - Mercur Messaging IMAP SUBSCRIBE Command Buffer Overflow, Moderately Critical
OSVDB: 33546 - MERCUR Messaging IMAP SUBSCRIBE Command Overflow
Vupen: ADV-2007-1092
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/13/2015 12:16Updated: 04/06/2019 08:51
Changes: 03/13/2015 12:16 (71), 04/06/2019 08:51 (5)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.