Spectra Assure

failRisk: Tampering

Scanned:

eyes_universal

Top 10k

Applitools Ruby Universal binaries for SDK

License: unknown

Published:

See on RubyGems

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

12 debugging symbols found

Security

Vulnerabilities

1 severe vulnerabilities exploited

Hardening

4 baseline mitigations missing

Threats

Tampering

2 signature compliance mistakes

Malware

No evidence of malware inclusion

INCIDENTS FOR THIS VERSION:

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

Policies

Info

Problem

Prevalence in RubyGems community

0 packages

found in

Top 100

0 packages

found in

Top 1k

12 packages

found in

Top 10k

196 packages

in community

Next steps

Review the certificate information passed to the code signing application.

If the problem persists, re-sign the software component with a newly acquired certificate, then publish the software package again.

Problem

Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.

Prevalence in RubyGems community

25 packages

found in

Top 100

118 packages

found in

Top 1k

1272 packages

found in

Top 10k

22.82k packages

in community

Next steps

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 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 RubyGems community

23 packages

found in

Top 100

93 packages

found in

Top 1k

1124 packages

found in

Top 10k

21.08k 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

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. Certificates have a validity period during which they can be used to create signatures. For application signatures, or digital code signing, it is recommended to countersign the signatures for time-stamping. Countersigned software components have their signature period validity extended past the signing certificate expiration date. Such signatures are considered valid indefinitely. We detected that the digital signature was not countersigned for time-stamping, and that the signing certificate has expired. Failing to countersign software components may result in application errors and availability outages.

Prevalence in RubyGems community

2 packages

found in

Top 100

2 packages

found in

Top 1k

18 packages

found in

Top 10k

261 packages

in community

Next steps

Acquire a new certificate and re-sign the software component.

Apply the optional time-stamping countersignature during signing.

With Microsoft SignTool, you can specify the trusted remote time-stamping server using the /t or /tr parameter.

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 high severity.

Prevalence in RubyGems community

36 packages

found in

Top 100

157 packages

found in

Top 1k

1717 packages

found in

Top 10k

29.81k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update 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

Operating systems execute application code in multiple privilege access levels. Separation of privileges is designed to protect the stability and integrity of the operating system by shielding it from issues that the user run applications may cause. However, some users may need to interact with higher privilege parts of the operating system to accomplish specific tasks. For this purpose, operating systems provide facilities that users may leverage to temporarily elevate their running privileges. Users with higher privileges can run any application with the same privilege level as their own. Attackers often try to trick privileged users into running malicious code, enabling them to infect the operating system. While the presence of code that elevates user privileges does not necessarily imply malicious intent, all of its uses in a software package should be documented and approved. Only select applications should consider using functions that can elevate user privileges. One example of acceptable use for such functions is allowing the users to install software packages and updates.

Prevalence in RubyGems community

1 packages

found in

Top 100

8 packages

found in

Top 1k

60 packages

found in

Top 10k

1.13k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1548 - Abuse Elevation Control Mechanism.

Consider rewriting the flagged code without using the marked behaviors.

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. Software developers publish components they have authored to public repositories. Some open source projects have a history of security lapses that culminated with a publication of one or more malicious component versions. To ensure that repeated supply chain incidents do not occur, the open source project should be closely monitored for up to two years. All software package versions that are published within two years of the malware incident will convey a warning about the history of security incidents tied to the open source project.

Prevalence in RubyGems community

1 packages

found in

Top 100

3 packages

found in

Top 1k

41 packages

found in

Top 10k

294 packages

in community

Next steps

Inspect behaviors exhibited by the detected software components.

If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.

Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.

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

Problem

Security Development Lifecycle (SDL) is a group of enhanced compile-time checks that report common coding mistakes as errors, preventing them from reaching production. These checks minimize the number of security issues by enforcing strict memory access checks. They also prevent the use of hard-to-secure string and memory manipulation functions. To prove the binary has been compiled with these checks enabled, the compiler emits a special debug object. Removing the debug table eliminates this proof. Therefore, this check only applies to binaries that still have their debug tables.

Prevalence in RubyGems community

0 packages

found in

Top 100

2 packages

found in

Top 1k

20 packages

found in

Top 10k

668 packages

in community

Next steps

You should keep the debug table to prove that the SDL process has been followed.

To enable these checks, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

Problem

Buffer overrun protection on Linux is achieved in two ways. The most common solution is to use the stack canary (also called cookie). The stack canary is a special value written onto the stack that allows the operating system to detect and terminate the program if a stack overrun occurs. In most cases, compilers will apply the stack canary conservatively in order to avoid a negative performance impact. Therefore, stack canaries are often used together with another stack overrun mitigation - fortified functions. Fortified functions are usually wrappers around standard glibc functions (such as memcpy) which perform boundary checks either at compile time or run time to determine if a memory violation has occurred. The compiler needs additional context to generate such calls (for example, array size that needs to be known at compile time). Because of this, the compiler will virtually never substitute all viable functions with their fortified counterparts in complex programs. However, when combined with the stack canary, fortified functions provide a good measure of buffer overrun protection.

Prevalence in RubyGems community

0 packages

found in

Top 100

12 packages

found in

Top 1k

62 packages

found in

Top 10k

1.29k packages

in community

Next steps

Presence of unfortified string functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

Problem

Prevalence in RubyGems community

0 packages

found in

Top 100

11 packages

found in

Top 1k

76 packages

found in

Top 10k

1.75k packages

in community

Next steps

Presence of unfortified memory functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

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

Prevalence in RubyGems community

0 packages

found in

Top 100

0 packages

found in

Top 1k

12 packages

found in

Top 10k

196 packages

in community

Next steps

Review the certificate information passed to the code signing application.

If the problem persists, re-sign the software component with a newly acquired certificate, then publish the software package again.

Problem

Prevalence in RubyGems community

25 packages

found in

Top 100

118 packages

found in

Top 1k

1272 packages

found in

Top 10k

22.82k packages

in community

Next steps

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 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 RubyGems community

23 packages

found in

Top 100

93 packages

found in

Top 1k

1124 packages

found in

Top 10k

21.08k 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 RubyGems community

2 packages

found in

Top 100

2 packages

found in

Top 1k

18 packages

found in

Top 10k

261 packages

in community

Next steps

Acquire a new certificate and re-sign the software component.

Apply the optional time-stamping countersignature during signing.

With Microsoft SignTool, you can specify the trusted remote time-stamping server using the /t or /tr parameter.

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 high severity.

Prevalence in RubyGems community

36 packages

found in

Top 100

157 packages

found in

Top 1k

1717 packages

found in

Top 10k

29.81k packages

in community

Next steps

Perform impact analysis for the reported CVEs.

Update 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 RubyGems community

1 packages

found in

Top 100

8 packages

found in

Top 1k

60 packages

found in

Top 10k

1.13k packages

in community

Next steps

Investigate reported detections as indicators of software tampering.

Consult Mitre ATT&CK documentation: T1548 - Abuse Elevation Control Mechanism.

Consider rewriting the flagged code without using the marked behaviors.

Problem

Prevalence in RubyGems community

1 packages

found in

Top 100

3 packages

found in

Top 1k

41 packages

found in

Top 10k

294 packages

in community

Next steps

Inspect behaviors exhibited by the detected software components.

If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.

Revise the use of components that raise these alarms. If you can't deprecate those components, make sure that their versions are pinned.

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

Problem

Prevalence in RubyGems community

0 packages

found in

Top 100

2 packages

found in

Top 1k

20 packages

found in

Top 10k

668 packages

in community

Next steps

You should keep the debug table to prove that the SDL process has been followed.

To enable these checks, refer to your programming language toolchain documentation.

In Microsoft VisualStudio, you can enable this feature by setting the compiler option /SDL to ON.

Problem

Prevalence in RubyGems community

0 packages

found in

Top 100

12 packages

found in

Top 1k

62 packages

found in

Top 10k

1.29k packages

in community

Next steps

Presence of unfortified string functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

Problem

Prevalence in RubyGems community

0 packages

found in

Top 100

11 packages

found in

Top 1k

76 packages

found in

Top 10k

1.75k packages

in community

Next steps

Presence of unfortified memory functions may indicate use of unsafe programming practices, and you should avoid it if possible.

In GCC, enable fortified functions with -fstack-protector and -D_FORTIFY_SOURCE=2 flag, while using at least -O1 optimization level.

eyes_universal

SAFE Assessment

Compliance

Security

Threats

IMPORTANT: This package had 8 malicious incidents in versions published within 2 years prior to the latestLatest version with malware incident detected: 3 months agoVersion: 4.56.0

INCIDENTS FOR THIS VERSION:

SQ20122Detected digital signatures used for code signing that do not have code signing listed for their intended use.Causes risk: signature compliance mistakessignatures

Problem

Prevalence in RubyGems community

Next steps

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in RubyGems community

Next steps

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

Problem

Prevalence in RubyGems community

Next steps

SQ20106Detected expired digital signatures that have not been countersigned for time-stamping.signatures

Problem

Prevalence in RubyGems community

Next steps

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in RubyGems community

Next steps

TH16120Detected presence of software components that can elevate the user privileges.hunting

Problem

Prevalence in RubyGems community

Next steps

TH30101Detected presence of software components that had a recent malware or tampering incident.Causes risk: components with malware historyhunting

Problem

Prevalence in RubyGems community

Next steps

SQ14138Detected Windows executable files that were compiled without following the recommended SDL process.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in RubyGems community

Next steps

SQ18105Detected Linux executable files compiled without any kind of buffer overrun protection while using banned string functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in RubyGems community

Next steps

SQ18106Detected Linux executable files compiled without any kind of buffer overrun protection while using banned memory functions.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in RubyGems community

Next steps

Did you know...

SQ20122Detected digital signatures used for code signing that do not have code signing listed for their intended use.Causes risk: signature compliance mistakessignatures

Problem

Prevalence in RubyGems community

Next steps

SQ31102Detected presence of severe vulnerabilities with active exploitation.Causes risk: actively exploited vulnerabilitiesvulnerabilities

Problem

Prevalence in RubyGems community

Next steps

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

Problem

Prevalence in RubyGems community

Next steps

SQ20106Detected expired digital signatures that have not been countersigned for time-stamping.signatures

Problem

Prevalence in RubyGems community

Next steps

SQ31105Detected presence of high severity vulnerabilities.Causes risk: high severity vulnerabilitiesvulnerabilities

Problem

Prevalence in RubyGems community

Next steps

TH16120Detected presence of software components that can elevate the user privileges.hunting

Problem

Prevalence in RubyGems community

Next steps

TH30101Detected presence of software components that had a recent malware or tampering incident.Causes risk: components with malware historyhunting

Problem

Prevalence in RubyGems community

Next steps

SQ14138Detected Windows executable files that were compiled without following the recommended SDL process.Causes risk: misconfigured toolchains detectedhardening

Problem

Prevalence in RubyGems community

Next steps