Top issues
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 NuGet community
0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
1437 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.
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
733240 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.
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
732229 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.
Top behaviors
Executes a file.
execution
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
12 packages
found in
Top 1k
98 packages
found in
Top 10k
39014 packages
in community
Elevates current user privileges.
execution
Prevalence in NuGet community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
4 packages
found in
Top 10k
1449 packages
in community
Contains URLs.
network
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
63 packages
found in
Top 1k
513 packages
found in
Top 10k
735907 packages
in community
Deletes a file/directory.
file
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
16 packages
found in
Top 1k
142 packages
found in
Top 10k
59206 packages
in community
Contains compression libraries.
signature
Prevalence in NuGet community
Behavior often found in this community (Common)
0 packages
found in
Top 100
11 packages
found in
Top 1k
112 packages
found in
Top 10k
35884 packages
in community
Top vulnerabilities
No vulnerabilities found.