Layton Technology HelpBox 3.7.1 editrequestenduser.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.0$0-$5k0.00

Summaryinfo

A vulnerability was found in Layton Technology HelpBox 3.7.1. It has been classified as critical. Affected by this issue is some unknown functionality of the file editrequestenduser.asp. Performing a manipulation of the argument sys_request_id results in sql injection. This vulnerability is reported as CVE-2007-5402. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical has been found in Layton Technology HelpBox 3.7.1. This affects an unknown code block of the file editrequestenduser.asp. 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.7.1 allow (1) remote attackers to execute arbitrary SQL commands via the sys_request_id parameter to editrequestenduser.asp; and allow remote authenticated users to execute arbitrary SQL commands via (2) the oldpassword parameter to writepwdenduser.asp, and the sys_request_id parameter to (3) changerequeststatus.asp, (4) editrequestuser.asp, (5) requestcommentsuser.asp, and (6) useractions.asp, different vectors than CVE-2004-2551.

The weakness was disclosed 01/09/2008 with Secunia Research (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-5402 since 10/12/2007. The exploitability is told to be easy. It is possible to initiate the attack remotely. The requirement for exploitation is a authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

It is declared as highly functional. By approaching the search of inurl:editrequestenduser.asp it is possible to find vulnerable targets with Google Hacking.

The vulnerability is also documented in the databases at X-Force (39539), SecurityFocus (BID 27187†) and Secunia (SA27699†). The entries VDB-40439, VDB-40438 and VDB-40436 are pretty similar. 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: 6.3
VulDB Meta Temp Score: 6.0

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: 🔍
Status: Highly functional
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

10/12/2007 🔍
01/08/2008 +88 days 🔍
01/09/2008 +1 days 🔍
01/09/2008 +0 days 🔍
03/16/2015 +2623 days 🔍
09/14/2018 +1278 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Organization: Secunia Research
Status: Confirmed

CVE: CVE-2007-5402 (🔍)
GCVE (CVE): GCVE-0-2007-5402
GCVE (VulDB): GCVE-100-40437
X-Force: 39539 - HelpBox sys_request_id parameter SQL injection
SecurityFocus: 27187 - HelpBox Multiple Security Vulnerabilities
Secunia: 27699

See also: 🔍

Entryinfo

Created: 03/16/2015 13:43
Updated: 09/14/2018 08:14
Changes: 03/16/2015 13:43 (50), 09/14/2018 08:14 (7)
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!