← Back to the full report
Verilay · IT Review Pack

juice-shop/juice-shop

Source: GitHub repository · Scanned: 31 Oct 2026, 14:12 UTC · Report ID: 8d5074779b8a
Suggested decision
Don't approve yet
Risk level
High
To fix
16 critical · 40 other

Critical issues must be fixed and the app scanned again before approval.

This is a suggestion based on the checks below. The approval decision belongs to the reviewer.

1 · Rule-based checks (repeatable)

The same code always gives the same result. Rule-based checks covered 1172 files. The AI review read the 150 most security-relevant files of 1172.

CheckResultStatusRelated standard
Exposed secrets
API keys, passwords and tokens written into the code
3 critical, 27 warnings across 1172 filesFailASVS 4.0.3 V6.4 Secret Management · CWE-798
Known-vulnerable libraries
Packages checked against the OSV.dev vulnerability database
20 vulnerable packages (3 serious) in 170 packages you installed directlyFailASVS 4.0.3 V14.2 Dependency · Top 10 2021 A06
Weak cryptography
Outdated hashes, broken cipher modes, hardcoded keys, small RSA keys
0 issues across 1172 files
Check required: no weak pattern was confirmed, but one thing needs a person to look: An old hash (MD5 or SHA-1) is used, and this app also handles passwords (lib/insecurity.ts line 41). It may or may not be connected, so check what that hash protects. This check only covers four specific patterns and does not review other cryptography.
Check requiredASVS 4.0.3 V6.2 Algorithms · Top 10 2021 A02
Who can do what
Database access rules and login checks on backend functions (Supabase apps)
Not applicable (no Supabase database or function files found), or not run for this reportNot checkedASVS 4.0.3 V4 Access Control · Top 10 2021 A01

2 · AI review by area (expert opinion)

Written by an AI model reading the code. Treat it as an informed opinion: results can vary slightly between runs, and "no issues found" means none were seen in the files read, not that the area is proven secure.

AreaFindingsStatusRelated standard
Auth
Login, sessions and who can do what
Private signing key committed in the code (confirmed scan); Login bypass via SQL injection; Anyone can register as an admin and some routes lack login checks; +2 moreFailASVS 4.0.3 V2 Authentication, V3 Session Management · Top 10 2021 A07
Database
How data is stored and who can read it
SQL injection in product search and review lookups exposes all data; Auto-generated endpoints expose sensitive tables and data is wiped on start; Sensitive user fields stored with little protectionFailASVS 4.0.3 V4 Access Control, V5 Validation · Top 10 2021 A01, A03
API
The app's server endpoints and what they accept
Missing auth on product updates plus open file and metrics endpoints; Data export reads any user's memories via client-supplied UserId; Risky handling of uploads, templates and server-side web requests; +2 moreFailASVS 4.0.3 V13 API and Web Service · Top 10 2021 A01
Config
Settings, environment variables and deployment setup
Private key files committed in infrastructure setup (confirmed scan); Open cross-origin access, hardcoded cookie secret and publicly browsable sensitive folders; Hard-coded credentials in source code; +1 moreFailASVS 4.0.3 V14 Configuration · Top 10 2021 A05
Frontend
What runs in the user's browser
Sample login tokens (JWTs) in front-end test files (confirmed scan); Login token stored in script-readable storage and test credentials in code; User text and files reach pages without cleaning (XSS risk); +1 moreNeeds fixesASVS 4.0.3 V5 Validation, Sanitization and Encoding · Top 10 2021 A03
Libraries
Third-party packages the app depends on
Critical flaws in jsonwebtoken, marsdb and sequelize; High-severity flaws in login, text-cleaning and server packages; High-severity flaws in Angular packages; +1 moreFailASVS 4.0.3 V14.2 Dependency · Top 10 2021 A06

3 · Fix before approval

  1. Critical Private Key File infrastructure/terraform/networking.tf:171
    Delete the key from the repository, generate a new one, and never store private keys in code.
  2. Critical Private Key File lib/insecurity.ts:21
    Delete the key from the repository, generate a new one, and never store private keys in code.
  3. Critical Private Key File terraform/networking.tf:171
    Delete the key from the repository, generate a new one, and never store private keys in code.
  4. Critical 20 vulnerable packages in libraries dependency files
    Update the affected packages to their fixed versions, then scan again.
  5. Critical Auth: Private signing key committed in the code (confirmed scan) lib/insecurity.ts
    A private key is the master stamp that makes login passes believable. If it is public, anyone can stamp a pass saying they are the shop owner.
  6. Critical Auth: Login bypass via SQL injection routes/login.ts
    Anyone on the internet can become any customer or the admin, leading to stolen data, fake orders and lost trust.
  7. Critical Auth: Anyone can register as an admin and some routes lack login checks server.ts
    If anyone can make themselves an admin or edit products without logging in, you do not control your shop's data and prices.
  8. Critical Auth: Password can be changed without knowing the current one routes/changePassword.ts
    Anyone with a borrowed or stolen session can permanently take over an account.
  9. Critical Auth: Predictable password for Google sign-in accounts frontend/src/app/oauth/oauth.component.ts
    Any customer who signed in with Google can have their account taken over by someone who only knows their email.
  10. Critical Config: Private key files committed in infrastructure setup (confirmed scan) infrastructure/terraform/networking.tf
    Infrastructure keys can unlock the servers the app runs on, not just the app itself.
  11. Critical Database: SQL injection in product search and review lookups exposes all data routes/search.ts
    A single search box can leak every customer's login details and let attackers map your whole database.
  12. Critical API: Missing auth on product updates plus open file and metrics endpoints server.ts
    Strangers could change prices, read server logs and secret keys, and register as administrators.
  13. Critical API: Data export reads any user's memories via client-supplied UserId routes/dataExport.ts
    A data export that leaks other customers' personal content is a privacy breach with possible legal exposure.
  14. Critical Libraries: Critical flaws in jsonwebtoken, marsdb and sequelize package.json
    These packages handle login passes and database queries, so flaws in them can let attackers fake logins or run their own database commands.
  15. Critical Libraries: High-severity flaws in login, text-cleaning and server packages package.json
    These can let attackers bypass login checks or freeze the server with crafted requests.
  16. Critical Libraries: Moderate and low issues across many packages package.json
    Individually smaller, but together they widen the ways attackers could inject scripts, forge logs or exploit shared settings.
  17. Warning JSON Web Token frontend/src/app/app.guard.spec.ts:46
    Remove it. If it belongs to a real account, sign that account out everywhere.
  18. Warning JSON Web Token frontend/src/app/last-login-ip/last-login-ip.component.spec.ts:72
    Remove it. If it belongs to a real account, sign that account out everywhere.
  19. Warning JSON Web Token frontend/src/app/last-login-ip/last-login-ip.component.spec.ts:78
    Remove it. If it belongs to a real account, sign that account out everywhere.
  20. Warning Generic Hardcoded Secret test/api/2fa.test.ts:42
    If it is a real secret, move it to an environment variable. If it is a placeholder, you can ignore this.
  21. Warning Generic Hardcoded Secret test/api/2fa.test.ts:66
    If it is a real secret, move it to an environment variable. If it is a placeholder, you can ignore this.
  22. Warning Generic Hardcoded Secret test/api/2fa.test.ts:85
    If it is a real secret, move it to an environment variable. If it is a placeholder, you can ignore this.
  23. Warning Generic Hardcoded Secret test/api/2fa.test.ts:104
    If it is a real secret, move it to an environment variable. If it is a placeholder, you can ignore this.
  24. Warning Generic Hardcoded Secret test/api/2fa.test.ts:123
    If it is a real secret, move it to an environment variable. If it is a placeholder, you can ignore this.
  25. Warning Generic Hardcoded Secret test/api/2fa.test.ts:142
    If it is a real secret, move it to an environment variable. If it is a placeholder, you can ignore this.
  26. +31 more in the full report

4 · What this review did not check

5 · Confirm independently

Free, widely used tools your team can run without Verilay:

WhatTool
Known-vulnerable librariesOSV-Scanner (google/osv-scanner)
Code security bugsSemgrep community rules
Secrets in code and historyGitleaks
Live site, passive scan (with the owner's permission)OWASP ZAP baseline scan

6 · Sign-off

Reviewed by: Date:
Decision:ApproveApprove with fixesDon't approve
Conditions or notes:

Generated by Verilay (verilay.dev) from report 8d5074779b8a. AI-assisted analysis may contain false positives or miss issues. Not a professional security audit. See verilay.dev/ai-disclaimer.