Beehive Forum Error Message index.php sort_by information disclosure

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.
5.3$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Beehive Forum. The affected element is an unknown function of the file index.php of the component Error Message Handler. Performing a manipulation of the argument sort_by results in information disclosure. This vulnerability is identified as CVE-2005-2423. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Beehive Forum (Forum Software) (the affected version is unknown). This affects an unknown code of the file index.php of the component Error Message Handler. The manipulation of the argument sort_by with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

Beehive Forum allows remote attackers to obtain sensitive information via (1) an invalid final_uri or sort_by parameter to index.php or a direct request to (2) admin.php, (3) attachments.inc.php, (4) banned.inc.php, (5) beehive.inc.php, (6) constants.inc.php, (7) db.inc.php, (8) dictionary.inc.php or (9) search_index.php, which reveal the path in an error message.

The weakness was released 08/03/2005 by thegreatone2176 (Website). It is possible to read the advisory at marc.theaimsgroup.com. This vulnerability is uniquely identified as CVE-2005-2423 since 08/03/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at X-Force (21536), SecurityFocus (BID 14363†) and Secunia (SA16217†). Entries connected to this vulnerability are available at VDB-25910 and VDB-25909. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

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

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/25/2005 🔍
07/26/2005 +1 days 🔍
08/03/2005 +8 days 🔍
08/03/2005 +0 days 🔍
08/03/2005 +0 days 🔍
03/11/2015 +3507 days 🔍
07/29/2017 +871 days 🔍

Sourcesinfo

Advisory: marc.theaimsgroup.com
Researcher: thegreatone2176
Status: Not defined

CVE: CVE-2005-2423 (🔍)
GCVE (CVE): GCVE-0-2005-2423
GCVE (VulDB): GCVE-100-25911
X-Force: 21536 - Beehive path disclosure
SecurityFocus: 14363 - Beehive Forum Webtag Multiple Cross-Site Scripting Vulnerabilities
Secunia: 16217 - Beehive Forum "webtag" SQL Injection Vulnerability, Moderately Critical

See also: 🔍

Entryinfo

Created: 03/11/2015 23:39
Updated: 07/29/2017 17:51
Changes: 03/11/2015 23:39 (57), 07/29/2017 17:51 (3)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!