Spectra Assure
Community
warningRisk: Secrets
Scanned: 5 days ago

Azure Load Testing

Artifact:
latest
An extension to create and run load tests using Azure Load Testing.
License: Permissive (MIT)
Published: 7 months ago

Publisher: ms-azure-load-testing



SAFE Assessment

Compliance

Licenses
No license compliance issues
Secrets
1 web service credentials found

Security

Vulnerabilities
No known vulnerabilities detected
Hardening
No application hardening issues

Threats

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

INCIDENTS FOR THIS VERSION:

Popularity

391.57k
Total Installs
Contributor
Declared Dependencies
0
Dependents

Top issues

Problem

Various network communication protocols allow including plaintext authentication credentials. Information such as user names and passwords could be passed through a non-encrypted channel, and therefore intercepted by malicious actors. Credentials are considered secrets, and should be kept encrypted until they are used. This policy control matches the following URI pattern protocol://username:password@domain within any software package component.

Prevalence in Visual Studio Code community

14 packages
found in
Top 100
112 packages
found in
Top 1k
273 packages
found in
Top 10k
1.71k packages
in community

Next steps

Review the reported matches. If the warning refers to a placeholder credential value, it can be safely ignored.

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. A port number is associated with a network address of a host, such as an IP address, and the type of network protocol used for communication. Within URLs, the ports are optional. Ports can be specified in a URL immediately following the domain name. Each network protocol, or schema, has a set of standard ports on which the service operates. This issue is raised when a mismatch between a network protocol and its expected port number is detected. While the presence of non-standard ports does not imply malicious intent, all of their uses in a software package should be documented and approved.

Prevalence in Visual Studio Code community

79 packages
found in
Top 100
560 packages
found in
Top 1k
2912 packages
found in
Top 10k
17.75k 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.
Consider changing the port to one that is standard for the networking protocol.

Top behaviors

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
84 packages
found in
Top 100
679 packages
found in
Top 1k
4393 packages
found in
Top 10k
30.42k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
82 packages
found in
Top 100
636 packages
found in
Top 1k
3971 packages
found in
Top 10k
25.82k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
40 packages
found in
Top 100
282 packages
found in
Top 1k
1349 packages
found in
Top 10k
7.08k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
74 packages
found in
Top 100
578 packages
found in
Top 1k
3262 packages
found in
Top 10k
18.65k packages
in community

Prevalence in Visual Studio Code community

Behavior often found in this community (Common)
54 packages
found in
Top 100
378 packages
found in
Top 1k
1783 packages
found in
Top 10k
7.78k packages
in community

Top vulnerabilities

No vulnerabilities found.