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
Dependency Confusion PossibleCVSS 8.1 · CWE-427Internal package names are not reserved on public registries and builds can fetch from both, so an attacker can publish a same-named public package that is installed instead.Secrets Committed to Source ControlCVSS 8.1 · CWE-540Passwords, API keys, tokens or private keys are stored in a source code repository or its history, where anyone with read access to the repository can use them.Secrets Exposed in CI/CD Logs or ConfigurationCVSS 8.1 · CWE-538Credentials used by build and deployment pipelines appear in job logs, pipeline definitions, unprotected variables or build artefacts readable by people who should not have them.Untrusted Input in CI/CD WorkflowsCVSS 8.1 · CWE-94A CI/CD workflow puts attacker-controllable data, such as pull request titles or branch names, into scripts it runs, or runs untrusted code with access to secrets.Over-Privileged CI/CD Pipeline CredentialsCVSS 7.5 · CWE-250Build and deployment pipelines run with credentials far broader than their tasks need, so any compromise of a pipeline gives wide control of cloud, code and production systems.Hard-Coded Cryptographic KeysCVSS 7.4 · CWE-321Encryption or signing keys are written into source code or shipped inside the application, so anyone who obtains the code can decrypt its data or forge what it signs.
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
Web Applications 87Authentication and Sessions 32APIs 16TLS and Certificates 20Network Services 56Internal Networks 9Active Directory 44Windows and Linux Hosts 29Patching and Outdated Software 36AWS 19Azure and Microsoft 365 19Google Cloud 11Containers and Kubernetes 17Mobile Applications 22Wireless 11Email and DNS 11Thick Clients 11AI and LLM Applications 8Social Engineering and Physical 14IoT and OT 5