Pmail Mercury Mail Transport System up to 4.01b Login stack-based overflow

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
10.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Pmail Mercury Mail Transport System up to 4.01b. It has been rated as critical. The affected element is an unknown function of the component Login. The manipulation leads to stack-based overflow. This vulnerability is referenced as CVE-2007-1373. Furthermore, an exploit is available.

Detailsinfo

A vulnerability, which was classified as very critical, has been found in Pmail Mercury Mail Transport System up to 4.01b. This issue affects an unknown function of the component Login. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Stack-based buffer overflow in Mercury/32 (aka Mercury Mail Transport System) 4.01b and earlier allows remote attackers to execute arbitrary code via a long LOGIN command. NOTE: this might be the same issue as CVE-2006-5961.

The weakness was published 03/06/2007 by mu-b (Website). The advisory is shared at lists.grok.org.uk. The identification of this vulnerability is CVE-2007-1373 since 03/09/2007. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/09/2017).

A public exploit has been developed by c0d3r and been published before and not just after the advisory. The exploit is available at saintcorporation.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 532 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. Attack attempts may be identified with Snort ID 1842.

The vulnerability is also documented in the databases at X-Force (32848), Exploit-DB (1223), OSVDB (33883†) and Secunia (SA24367†). Similar entry is available at VDB-33322. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 10.0

VulDB Base Score: 10.0
VulDB Temp Score: 10.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Highly functional
Author: c0d3r
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Saint ID: exploit_info/mercury_imap_continuation
Saint Name: Mercury IMAP data continuation buffer overflow

MetaSploit ID: mercury_login.rb
MetaSploit Name: Mercury/32 LOGIN Buffer Overflow
MetaSploit File: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Snort ID: 1842
Snort Message: PROTOCOL-IMAP login buffer overflow attempt
Snort Class: 🔍

Timelineinfo

09/20/2005 🔍
09/20/2005 +0 days 🔍
03/06/2007 +532 days 🔍
03/07/2007 +0 days 🔍
03/07/2007 +0 days 🔍
03/09/2007 +1 days 🔍
03/09/2007 +0 days 🔍
03/13/2015 +2926 days 🔍
10/09/2017 +941 days 🔍

Sourcesinfo

Advisory: lists.grok.org.uk
Researcher: mu-b
Status: Confirmed

CVE: CVE-2007-1373 (🔍)
GCVE (CVE): GCVE-0-2007-1373
GCVE (VulDB): GCVE-100-35525
X-Force: 32848 - Mercury Mail Transport System IMAP buffer overflow
Secunia: 24367 - Mercury Mail Transport System IMAP Data Handling Buffer Overflow, Highly Critical
OSVDB: 33883 - Mercury Mail Transport System IMAP LOGIN Command Remote Overflow

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/13/2015 12:16
Updated: 10/09/2017 16:57
Changes: 03/13/2015 12:16 (67), 10/09/2017 16:57 (8)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!