VDB-33773 · CVE-2006-6464 · BID 21500

Midicart Software Midicart Php Shopping Cart

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 was found in Midicart Software Midicart Php Shopping Cart. It has been classified as problematic. This vulnerability affects unknown code. The manipulation leads to an unknown weakness. This vulnerability is listed as CVE-2006-6464. There is no available exploit.

Detailsinfo

A vulnerability was found in Midicart Software Midicart Php Shopping Cart (Programming Language Software) (unknown version) and classified as problematic. Impacted is integrity. The summary by CVE is:

viewcart in Midicart accepts negative numbers in the Qty (quantity) field, which allows remote attackers to obtain a smaller total price for a shopping cart.

The weakness was presented 12/11/2006 by inversFX as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2006-6464 since 12/11/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly 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 21500†) and Secunia (SA23296†). See VDB-33772 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

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: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

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

12/07/2006 🔍
12/11/2006 +4 days 🔍
12/11/2006 +0 days 🔍
12/11/2006 +0 days 🔍
03/12/2015 +3013 days 🔍
10/03/2017 +936 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Researcher: inversFX
Status: Not defined

CVE: CVE-2006-6464 (🔍)
GCVE (CVE): GCVE-0-2006-6464
GCVE (VulDB): GCVE-100-33773
SecurityFocus: 21500 - MidiCart PHP Multiple Input Validation and Authenication Bypass Vulnerabilities
Secunia: 23296

See also: 🔍

Entryinfo

Created: 03/12/2015 22:21
Updated: 10/03/2017 12:22
Changes: 03/12/2015 22:21 (50), 10/03/2017 12:22 (1)
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 ▸

Do you need the next level of professionalism?

Upgrade your account now!