Source Code and Supply Chain Findings.

13 findings in source code and the supply chain, each written up as a report carries it: what the weakness is and what it lets an attacker do, the fix, CVSS 3.1 and 4.0 ratings, the CWE and the references.

High6

Medium7

Unpinned Third-Party Dependencies or ActionsCVSS 6.6 · CWE-494Builds pull third-party actions, packages or images by mutable tags or version ranges, so a change by an upstream owner or attacker is used automatically without review.Branch Protection Not EnforcedCVSS 6.5 · CWE-266Main and release branches accept direct pushes, force pushes or unreviewed merges, so a single account can change the code that is built and deployed without review.Use of Unsafe Memory FunctionsCVSS 6.5 · CWE-676C or C++ code uses functions such as strcpy, strcat, sprintf or gets that do not check buffer sizes, risking buffer overflows when input is longer than expected.Use of Weak Cryptographic AlgorithmsCVSS 5.9 · CWE-327The code uses broken or outdated cryptographic algorithms, modes or key sizes, such as DES, RC4, MD5, SHA-1 or ECB mode, to protect data or check its integrity.Insecure Infrastructure-as-Code ConfigurationCVSS 5.6 · CWE-732Infrastructure templates such as Terraform, CloudFormation, Bicep or Kubernetes manifests define resources with insecure settings that are deployed wherever they are used.Third-Party Dependencies With Known VulnerabilitiesCVSS 5.6 · CWE-1395The application includes third-party libraries or packages at versions with publicly known vulnerabilities, some of which may be exploitable through the application.Insecure Randomness for Security ValuesCVSS 4.8 · CWE-338Tokens, identifiers or keys that must be unguessable are generated with a non-cryptographic random number generator whose output can be predicted.

The Other Areas

Every One of These, in Your Own Library.

In Pental the finding library is in Settings, Library: add the findings you write most, rated in your firm's CVSS version, and make them your own. Free trial, no card required.