failRisk: Vulnerabilities

Scanned:

BarcodeLib.BarcodeReader

latest

Barcode Reader for .NET is a C# barcode scanning library to read, scan QR Code, Data Matrix, Code 128 and other 2d and 1d barcode symbologies in your ASP.NET web and desktop applications. Barcode Reader for .NET is an advanced barcode scanner package : * Read, scan QR Code, Data Matrix, PDF-417, Code 39 / 128, EAN/UPC, Supplemental barcodes, GS1-128, and other 1d barcode formats * Recognise multiple barcodes from a single file with fast reading speed and high recognition rate * Support reading barcodes from GIF, BMP, JPEG, TIFF, PNG image files, and stream objects * Quick to scan and read barcodes from specified area inside the image Compatible with * .NET Standard 2.0 * .NET 8, .NET 7, .NET 6, .NET 5, .NET Core 3.x & 2.x * .NET Framework 4.x * Windows, MacOS, Linux, Docker, Azure Online Documents * C# How to Guide : https://www.barcodelib.com/csharp/barcode_reader_csharp.html * Licenses : https://www.barcodelib.com/purchase/license-barcode-reader-net.html * Email : support@barcodelib.com

License: unknown

Published:

See on NuGet

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

1 critical severity vulnerabilities

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

List of software quality issues with the number of affected components.

Policies

Info

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as critical severity.

Prevalence in NuGet community

0 packages

found in

Top 100

65 packages

found in

Top 1k

757 packages

found in

Top 10k

19.24k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.

Prevalence in NuGet community

0 packages

found in

Top 100

27 packages

found in

Top 1k

936 packages

found in

Top 10k

22.91k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Obfuscation is a process of mangling the software code legibility. Obfuscation can be applied to both the application source and its compiled code counterpart. In both cases, obfuscation can interfere with the accuracy of security and software quality assessment solutions. For this reason, obfuscation is a technique commonly used by malicious actors as a means of bypassing security solutions and avoiding detection. While presence of obfuscation does not imply malicious intent, all of its uses in a software package should be documented and approved. One example of acceptable use for code obfuscation is minimizing the size of script files that are not intended to be read by humans. In such a case, the trade-off between file size and code legibility is considered acceptable.

Prevalence in NuGet community

0 packages

found in

Top 100

4 packages

found in

Top 1k

459 packages

found in

Top 10k

6.53k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1027 - Obfuscated Files or Information.

Consider an alternative to code obfuscation to lower the risk of being mistakenly flagged by security solutions.

Problem

Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Open source communities depend on the work of thousands of software developers that volunteer their time to maintain software components. Software developers build up the reputation of their open source projects by developing in public. Modern source code repositories have many social features that allow software developers to handle bug reports, have discussions with their users, and convey reaching significant project milestones. It is uncommon to find open source projects that omit linking their component to a publicly accessible source code repository.

Prevalence in NuGet community

99 packages

found in

Top 100

723 packages

found in

Top 1k

6007 packages

found in

Top 10k

575.57k packages

in community

Next steps

Check the software component behaviors for anomalies.

Consider exploratory software component testing within a sandbox environment.

Consider replacing the software component with a more widely used alternative.

Avoid using this software package until it is vetted as safe.

Problem

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures verify the origin and the integrity of the object they apply to. The integrity validation relies on the cryptographic strength of the encryption and the hash verification algorithm. If either of the two is considered weak by current standards, there is a chance the signed object could be maliciously modified, without triggering the integrity failure check.

Prevalence in NuGet community

100 packages

found in

Top 100

899 packages

found in

Top 1k

8997 packages

found in

Top 10k

755.66k packages

in community

Next steps

Create signatures with strong ECC key-length of at least 224 bits, or RSA key-length of at least 2048 bits, and use SHA256 as the hashing algorithm. While encryption key-length upgrade does require you to obtain a new certificate, the hashing algorithm can freely be selected during signing.

With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

Problem

Digital signatures are applied to applications, packages and documents as a cryptographically secured authenticity record. Signatures are made using digital certificates, which can either be purchased from certificate authorities or be self-issued. When a certificate is purchased from a certificate authority, the subject that requests it goes through an identity validation process. Depending on the certificate type, those checks can be basic or extended. Confirming the subject identity is a multi-step process, and the requesting subject can be mapped to its legal entity name only through extended validation of submitted documents. Extended identity validation typically costs more, and it takes longer for a certificate to be issued when this process is correctly followed.

Prevalence in NuGet community

100 packages

found in

Top 100

898 packages

found in

Top 1k

8984 packages

found in

Top 10k

754.38k packages

in community

Next steps

Consider the benefits of acquiring extended validation certificates. Operating systems tend to be more trusting of software packages signed in this way. Certain security warnings and prompts might also be automatically suppressed. This reduces the number of support tickets for organizations that opt to use extended validation certificates.

Did you know...

... that you can use ReversingLabs’ Spectra Assure platform to perform regular risk assessments of packages you develop in-house?

We recommend continuous software safeness monitoring through CI/CD integrations and pre-release/deployment checks. In addition to basic package information found on this page our platform offers rich reports for developers and DevSecOps that help them remediate all reported issues.

This website uses cookies to ensure the best website experience. By continuing to use this website you are giving your consent to cookies being used. Detailed information about our use of cookies is here.

List of software quality issues with the number of affected components.

Policies

Info

Problem

Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as critical severity.

Prevalence in NuGet community

0 packages

found in

Top 100

65 packages

found in

Top 1k

757 packages

found in

Top 10k

19.24k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

We strongly advise updating the component to the latest version.

If the update can't resolve the issue, create a plan to isolate or replace the affected component.

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

27 packages

found in

Top 1k

936 packages

found in

Top 10k

22.91k packages

in community

Next steps

Investigate reported detections.

If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.

You should delay the software release until the investigation is completed, or until the issue is risk accepted.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

4 packages

found in

Top 1k

459 packages

found in

Top 10k

6.53k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1027 - Obfuscated Files or Information.

Consider an alternative to code obfuscation to lower the risk of being mistakenly flagged by security solutions.

Problem

Prevalence in NuGet community

99 packages

found in

Top 100

723 packages

found in

Top 1k

6007 packages

found in

Top 10k

575.57k packages

in community

Next steps

Check the software component behaviors for anomalies.

Consider exploratory software component testing within a sandbox environment.

Consider replacing the software component with a more widely used alternative.

Avoid using this software package until it is vetted as safe.

Problem

Prevalence in NuGet community

100 packages

found in

Top 100

899 packages

found in

Top 1k

8997 packages

found in

Top 10k

755.66k packages

in community

Next steps

With Microsoft SignTool, you can specify the hashing algorithm using the /fd SHA256 parameter.

Problem

Prevalence in NuGet community

100 packages

found in

Top 100

898 packages

found in

Top 1k

8984 packages

found in

Top 10k

754.38k packages

in community

BarcodeLib.BarcodeReader

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 1 removal incident in versions published within 2 years prior to the latestLatest version with removal incident detected: about 1 year agoVersion: 7.4.1

INCIDENTS FOR THIS VERSION:

SQ31104Detected presence of critical severity vulnerabilities.Causes risk: critical severity vulnerabilitiesvulnerabilities

Problem

Prevalence in NuGet community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in NuGet community

Next steps

TH16101Detected presence of obfuscated software components.hunting

Problem

Prevalence in NuGet community

Next steps

TH30112Detected presence of software components without a declared source code repository.hunting

Problem

Prevalence in NuGet community

Next steps

SQ20119Detected digital signatures that rely on a weak digest algorithm for integrity validation.signatures

Problem

Prevalence in NuGet community

Next steps

SQ20121Detected digital signatures that have not been performed with an extended validation certificate.signatures

Problem

Prevalence in NuGet community

Next steps

Did you know...

SQ31104Detected presence of critical severity vulnerabilities.Causes risk: critical severity vulnerabilitiesvulnerabilities

Problem

Prevalence in NuGet community

Next steps

TH15103Detected presence of files with behaviors commonly used by malicious software.hunting

Problem

Prevalence in NuGet community

Next steps

TH16101Detected presence of obfuscated software components.hunting

Problem

Prevalence in NuGet community

Next steps

TH30112Detected presence of software components without a declared source code repository.hunting

Problem

Prevalence in NuGet community

Next steps

SQ20119Detected digital signatures that rely on a weak digest algorithm for integrity validation.signatures

Problem

Prevalence in NuGet community

Next steps

SQ20121Detected digital signatures that have not been performed with an extended validation certificate.signatures

Problem

Prevalence in NuGet community

Next steps