Bitflux Upload Progress Meter up to 8274 uploadprogress.c uploadprogress_php_rfc1867_file memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.7 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Bitflux Upload Progress Meter up to 8274 and classified as critical. This affects the function uploadprogress_php_rfc1867_file of the file uploadprogress.c. This manipulation causes memory corruption.
This vulnerability appears as CVE-2006-6361. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability has been found in Bitflux Upload Progress Meter up to 8274 and classified as critical. Affected by this vulnerability is the function uploadprogress_php_rfc1867_file of the file uploadprogress.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Heap-based buffer overflow in the uploadprogress_php_rfc1867_file function in uploadprogress.c in Bitflux Upload Progress Meter before 8276 allows remote attackers to cause a denial of service (crash) or execute arbitrary code via crafted HTTP POST fileupload requests.
The weakness was presented 12/07/2006 by Stefan Esser (Website). The advisory is shared at ssl.bitflux.ch. This vulnerability is known as CVE-2006-6361 since 12/06/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.
It is declared as proof-of-concept.
Upgrading to version 8275 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (30715) and SecurityFocus (BID 21417†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 8.7
VulDB Base Score: 10.0
VulDB Temp Score: 8.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Upload Progress Meter 8275
Timeline
12/04/2006 🔍12/06/2006 🔍
12/07/2006 🔍
12/07/2006 🔍
03/12/2015 🔍
10/03/2017 🔍
Sources
Advisory: ssl.bitflux.chResearcher: Stefan Esser
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2006-6361 (🔍)
GCVE (CVE): GCVE-0-2006-6361
GCVE (VulDB): GCVE-100-33673
X-Force: 30715 - Upload Progress Meter uploadprogress.c buffer overflow
SecurityFocus: 21417 - PHP Upload Progress Meter UploadProgress.C Remote Buffer Overflow Vulnerability
Vupen: ADV-2006-4841
Entry
Created: 03/12/2015 22:21Updated: 10/03/2017 12:18
Changes: 03/12/2015 22:21 (52), 10/03/2017 12:18 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.