warningRisk: Hardening

Scanned:

7-Zip.CommandLine

latest

7-Zip is a file archiver with a high compression ratio. 7za.exe is a standalone console version of 7-Zip with reduced formats support. 7za.exe and 7z.exe from 7-Zip have same command line interface. 7za.exe features: - High compression ratio in 7z format - Supported formats: - Packing / unpacking: 7z, xz, ZIP, GZIP, BZIP2 and TAR - Unpacking only: lzma, CAB, ZSTD. - Highest compression ratio for ZIP and GZIP formats. - Fast compression and decompression - Strong AES-256 encryption in 7z and ZIP formats. NOTE: This NuGet package was created by extracting the 7za.exe from 7-Zip Extra and adding the Help File (7-zip.chm) from 7-Zip.

License: Copyleft (LGPL-2.1-or-later)

Published:

See on NuGet

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

1 reduced effectiveness mitigations

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

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

Policies

Info

Problem

Protection from integer-based memory allocation overflow attacks is a vulnerability mitigation implemented by the programming language compiler. It enables enforcement of memory allocation limits during code execution. This is achieved by instrumenting each memory allocation instance (through the programming language keyword 'new') and validating its parameters. Should an application try to allocate a maximum number of elements via a single call to 'new', the execution will be terminated. This vulnerability mitigation is designed to protect against resource exhaustion and improper handling of memory allocation failures.

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

3 packages

found in

Top 10k

1.01k packages

in community

Next steps

Microsoft VisualStudio users can take advantage of this configuration-free vulnerability mitigation by updating to a newer compiler version. With this update, additional vulnerability mitigation options will also become available.

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

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

0 packages

found in

Top 1k

4 packages

found in

Top 10k

1.09k 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.

TH30112

Detected presence of software components without a declared source code repository.

hunting

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

No prevalence information at this time

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.

SQ14109

Detected Windows executable files that trigger ASLR compatibility mode and reduce its effectiveness.

Causes risk: reduced effectiveness mitigations

hardening

Problem

Address Space Layout Randomization (ASLR) is a vulnerability mitigation option that forces software components to load on a different memory base address each time they are used. This mitigation is detected as enabled, but rendered ineffective since the set load base address forces the 64-bit image to load within the lower 32-bit memory range. Having a smaller memory range makes ASLR more predictable, and it is therefore easier for malicious code to bypass it.

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

1.16k packages

in community

Next steps

Review the programming language linker options.

In Microsoft VisualStudio, you should check if the linker option /BASE is set to a value lesser than 4GB.

SQ14122

Detected Windows executable files that do not implement CFG vulnerability mitigation protection.

Causes risk: modern mitigations missing

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

2 packages

found in

Top 1k

38 packages

found in

Top 10k

9.4k packages

in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.

To enable this mitigation, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ14127

Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.

Causes risk: low priority mitigations absent

hardening

Problem

Control Flow Guard (CFG/CFI) protects the code flow integrity by ensuring that indirect calls are made only to vetted functions. This mitigation protects dynamically resolved function targets by instrumenting the code responsible for transferring execution control. Higher-level programming languages implement structured exception handling by managing their own code flow execution paths. As such, they are subject to code flow hijacking during runtime. Language-specific exception handling mitigation enforces execution integrity by instrumenting calls to manage execution context switching. Any deviation from the known and trusted code flow paths will cause the application to terminate. This makes malicious code less likely to execute.

Prevalence in NuGet community

0 packages

found in

Top 100

2 packages

found in

Top 1k

52 packages

found in

Top 10k

16.15k packages

in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.

To enable this mitigation, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ20119

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

signatures

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

0 packages

found in

Top 100

38 packages

found in

Top 1k

315 packages

found in

Top 10k

733.24k 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.

SQ20121

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

signatures

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

0 packages

found in

Top 100

27 packages

found in

Top 1k

292 packages

found in

Top 10k

732.23k 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.

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

Policies

Info

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

3 packages

found in

Top 10k

1.01k packages

in community

Next steps

TH15103

Detected presence of files with behaviors commonly used by malicious software.

hunting

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

4 packages

found in

Top 10k

1.09k 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.

TH30112

Detected presence of software components without a declared source code repository.

hunting

Problem

Prevalence in NuGet community

No prevalence information at this time

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.

SQ14109

Detected Windows executable files that trigger ASLR compatibility mode and reduce its effectiveness.

Causes risk: reduced effectiveness mitigations

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

0 packages

found in

Top 1k

6 packages

found in

Top 10k

1.16k packages

in community

Next steps

Review the programming language linker options.

In Microsoft VisualStudio, you should check if the linker option /BASE is set to a value lesser than 4GB.

SQ14122

Detected Windows executable files that do not implement CFG vulnerability mitigation protection.

Causes risk: modern mitigations missing

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

2 packages

found in

Top 1k

38 packages

found in

Top 10k

9.4k packages

in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.

To enable this mitigation, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ14127

Detected Windows executable files that do not implement long jump control flow vulnerability mitigation protection.

Causes risk: low priority mitigations absent

hardening

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

2 packages

found in

Top 1k

52 packages

found in

Top 10k

16.15k packages

in community

Next steps

It's highly recommended to enable this option for all software components used at security boundaries, or those that process user controlled inputs.

To enable this mitigation, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable CFG mitigation by passing the /guard:cf parameter to the compiler and linker.

SQ20119

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

signatures

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

38 packages

found in

Top 1k

315 packages

found in

Top 10k

733.24k packages

in community

Next steps

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

SQ20121

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

signatures

Problem

Prevalence in NuGet community

0 packages

found in

Top 100

27 packages

found in

Top 1k

292 packages

found in

Top 10k

732.23k packages

in community