Spectra Assure
Community
failRisk: Vulnerabilities
Scanned: 3 days ago

vuelidate

latest
Top 10k
Simple, lightweight model-based validation for Vue.js
License: Permissive (MIT)
Published: about 4 years ago



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
No sensitive information found

Security

Vulnerabilities
1 severe vulnerabilities exploited
Hardening
No application hardening issues

Threats

Tampering
No evidence of software tampering
Malware
No evidence of malware inclusion

Popularity

47.98M
Recorded Downloads Since 2021
Contributors
Declared Dependencies
534
Dependents

Top issues

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

24 packages
found in
Top 100
101 packages
found in
Top 1k
1359 packages
found in
Top 10k
511.03k 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 high severity.

Prevalence in npm community

22 packages
found in
Top 100
114 packages
found in
Top 1k
1440 packages
found in
Top 10k
528.88k 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

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

9 packages
found in
Top 100
29 packages
found in
Top 1k
255 packages
found in
Top 10k
95.32k 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

Uniform Resource Locators (URLs) are structured addresses that point to locations and assets on the internet. URLs allow software developers to build complex applications that exchange data with servers that can be hosted in multiple geographical regions. URLs can commonly be found embedded in documentation, configuration files, source code and compiled binaries. One or more embedded URLs were discovered to link to the file attachments hosted on Discord. Attackers often abuse popular web services to host malicious payloads. Since file-sharing services URLs are typically allowed by security solutions, using them for payload delivery increases the odds that the malicious code will reach the user. While the presence of Discord file-sharing locations does not imply malicious intent, no software should be directly linking to a Discord file attachment. An increasing number of software supply chain attacks in the open source space leverages the Discord file-sharing service to deliver malicious payloads.

Prevalence in npm community

0 packages
found in
Top 100
0 packages
found in
Top 1k
3 packages
found in
Top 10k
2k packages
in community

Next steps

Investigate reported detections.
If the software should not include these network references, 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.
Remove all references to flagged network locations.

Top behaviors

Prevalence in npm community

Behavior commonly used by malicious software (Important)
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
3 packages
found in
Top 10k
2k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
95 packages
found in
Top 100
726 packages
found in
Top 1k
7488 packages
found in
Top 10k
4.56M packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
26 packages
found in
Top 100
134 packages
found in
Top 1k
2067 packages
found in
Top 10k
896.14k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
33 packages
found in
Top 100
148 packages
found in
Top 1k
2322 packages
found in
Top 10k
692.01k packages
in community

Prevalence in npm community

Behavior often found in this community (Common)
72 packages
found in
Top 100
465 packages
found in
Top 1k
5356 packages
found in
Top 10k
1.75M packages
in community

Top vulnerabilities

Vulnerability Exploitation Lifecycle
(1 Active Vulnerabilities)
None
1 (0 Fixable)
CVE-2021-3794h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated