Blursoft blur6ex 0.3.462 index.php ID sql injection

entryeditHistoryDiffjsonxmlCTI
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

A vulnerability classified as critical was found in Blursoft blur6ex 0.3.462. Affected by this vulnerability is an unknown code block of the file index.php. The manipulation of the argument ID with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. As an impact it is known to affect integrity. An attacker might be able inject and/or alter existing SQL statements which would influence the database exchange. The summary by CVE is:

Multiple SQL injection vulnerabilities in index.php in blur6ex 0.3.452 allows remote attackers to execute arbitrary SQL commands via the ID parameter in a (1) g_reply or (2) g_permaPost action to the blog shard (engine/shards/blog.php), or a (3) g_viewContent action to the content shard (engine/shards/content.php).

The weakness was shared 04/12/2006 by Rusydi Hasan M (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2006-1763 since 04/12/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.

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 SecurityFocus (BID 17465) and X-Force (25759). The entries 29628 and 29627 are related to this item.

Productinfoedit

Vendor

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

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

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

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

NVD Base Score: 🔍

Exploitinginfoedit

Class: Sql injection
CWE: CWE-89
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

Threat: 🔍
Adversaries: 🔍
Geopolitics: 🔍
Economy: 🔍
Predictions: 🔍
Remediation: 🔍

Countermeasuresinfoedit

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfoedit

04/11/2006 🔍
04/12/2006 +1 days 🔍
04/12/2006 +0 days 🔍
04/12/2006 +0 days 🔍
03/12/2015 +3256 days 🔍
07/24/2018 +1230 days 🔍

Sourcesinfoedit

Advisory: securityfocus.com
Researcher: Rusydi Hasan M
Status: Not defined

CVE: CVE-2006-1763 (🔍)
SecurityFocus: 17465 - Blursoft Blur6ex Multiple Input Validation Vulnerabilities
X-Force: 25759 - blur6ex index.php SQL injection

See also: 🔍

Entryinfoedit

Created: 03/12/2015 12:19 PM
Updated: 07/24/2018 10:07 AM
Changes: (1) advisory_person_name
Complete: 🔍

Comments

No comments yet. Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!