VDB-82013 · SA11588 · OSVDB 6038

Mailenable Professional HTTPMail Service Authorization Header denial of service

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.
4.1	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Mailenable Professional. This affects an unknown function of the component HTTPMail Service. The manipulation as part of Authorization Header leads to denial of service. There is no available exploit.

Detailsinfo

A vulnerability was found in Mailenable Professional (Mail Server Software) (affected version unknown) and classified as problematic. This issue affects an unknown functionality of the component HTTPMail Service. The manipulation as part of a Authorization Header leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.

The weakness was presented 05/11/2004 by Behrang Fouladi (Website). The advisory is shared at oliverkarow.de. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.

A possible mitigation has been published 5 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at OSVDB (6038†) and Secunia (SA11588†). See VDB-23594, VDB-23593 and VDB-90806 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Mail Server Software

Name

Mailenable Professional

License

commercial

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

05/11/2004 🔍
05/11/2004 +0 days 🔍
05/16/2004 +4 days 🔍
04/11/2016 +4348 days 🔍
10/02/2018 +904 days 🔍

Sourcesinfo

Advisory: oliverkarow.de
Researcher: Behrang Fouladi
Status: Not defined

GCVE (VulDB): GCVE-100-82013
Secunia: 11588
OSVDB: 6038 - MailEnable Professional HTTPMail Service Authorization Header Handling Remote DoS

See also: 🔍

Entryinfo

Created: 04/11/2016 18:04
Updated: 10/02/2018 08:57
Changes: 04/11/2016 18:04 (43), 10/02/2018 08:57 (2)
Complete: 🔍
Cache ID: 216::103

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