Layton Technology Helpbox 3.0.1 User Account editcommentenduser.asp sys_request_id sql injection

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

Summaryinfo

A vulnerability marked as critical has been reported in Layton Technology Helpbox 3.0.1. This vulnerability affects unknown code of the file editcommentenduser.asp of the component User Account. Performing a manipulation of the argument sys_request_id results in sql injection. This vulnerability was named CVE-2004-2551. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in Layton Technology Helpbox 3.0.1. It has been classified as critical. This affects an unknown code of the file editcommentenduser.asp of the component User Account. The manipulation of the argument sys_request_id with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Multiple SQL injection vulnerabilities in Layton HelpBox 3.0.1 allow remote attackers to execute arbitrary SQL commands via (1) the sys_comment_id parameter in editcommentenduser.asp, (2) the sys_suspend_id parameter in editsuspensionuser.asp, (3) the table parameter in export_data.asp, (4) the sys_analgroup parameter in manageanalgrouppreference.asp, (5) the sys_asset_id parameter in quickinfoassetrequests.asp, (6) the sys_eusername parameter in quickinfoenduserrequests.asp, and the sys_request_id parameter in (7) requestauditlog.asp, (8) requestcommentsenduser.asp, (9) selectrequestapplytemplate.asp, and (10) selectrequestlink.asp, resulting in an ability to create a new HelpBox user account and read, modify, or delete data from the backend database.

The bug was discovered 04/15/2004. The weakness was presented 07/21/2004 by Noam Rathaus (SecuriTeam) with SecuriTeam.com (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2004-2551 since 11/21/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 and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 97 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:editcommentenduser.asp 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 (16772), Exploit-DB (24303), SecurityFocus (BID 10776†), OSVDB (8170†) and Secunia (SA12118†). See VDB-82117, VDB-82118, VDB-82119 and VDB-82120 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/15/2004 🔍
07/21/2004 +97 days 🔍
07/21/2004 +0 days 🔍
07/22/2004 +0 days 🔍
12/31/2004 +161 days 🔍
11/21/2005 +325 days 🔍
03/09/2015 +3395 days 🔍
03/29/2025 +3673 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Researcher: Noam Rathaus (SecuriTeam)
Organization: SecuriTeam.com
Status: Not defined

CVE: CVE-2004-2551 (🔍)
GCVE (CVE): GCVE-0-2004-2551
GCVE (VulDB): GCVE-100-23433
X-Force: 16772 - HelpBox multiple SQL injections
SecurityFocus: 10776 - Layton Technology HelpBox Multiple SQL Injection Vulnerabilities
Secunia: 12118
OSVDB: 8170 - HelpBox editcommentenduser.asp sys_comment_id Parameter SQL Injection

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

Entryinfo

Created: 03/09/2015 16:55
Updated: 03/29/2025 02:59
Changes: 03/09/2015 16:55 (64), 06/29/2018 10:34 (1), 03/29/2025 02:59 (27)
Complete: 🔍
Cache ID: 216:AAF:103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!