BarCodeWiz Barcode Activex up to 6.6 BarcodeWiz.DLL BottomText/TopText memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in BarCodeWiz Barcode Activex up to 6.6. This issue affects some unknown processing in the library BarcodeWiz.DLL. The manipulation of the argument BottomText/TopText as part of Long Argument leads to memory corruption. This vulnerability is listed as CVE-2018-5221. The attack may be initiated remotely. In addition, an exploit is available. You should upgrade the affected component.
Details
A vulnerability was found in BarCodeWiz Barcode Activex up to 6.6 and classified as critical. This issue affects some unknown functionality in the library BarcodeWiz.DLL. The manipulation of the argument BottomText/TopText as part of a Long Argument leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Multiple buffer overflows in BarCodeWiz BarCode before 6.7 ActiveX control (BarcodeWiz.DLL) allow remote attackers to execute arbitrary code via a long argument to the (1) BottomText or (2) TopText property.
The bug was discovered 01/06/2018. The weakness was presented 01/09/2018 (Website). The advisory is shared at hyp3rlinx.altervista.org. The identification of this vulnerability is CVE-2018-5221 since 01/05/2018. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known.
The exploit is available 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 3 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 6.7 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (43456). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.7
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Barcode Activex 6.7
Timeline
01/05/2018 🔍01/06/2018 🔍
01/09/2018 🔍
01/09/2018 🔍
01/10/2018 🔍
01/20/2023 🔍
Sources
Advisory: 145731Status: Not defined
CVE: CVE-2018-5221 (🔍)
GCVE (CVE): GCVE-0-2018-5221
GCVE (VulDB): GCVE-100-111533
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 01/10/2018 08:06Updated: 01/20/2023 13:04
Changes: 01/10/2018 08:06 (61), 12/20/2019 17:12 (4), 01/20/2023 13:04 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.