High severityJavaInsecure ConfigurationMEDIUM confidence
Permissive CORS Wildcard
CORS is configured to allow any origin with "*" (CWE-942).
Standards mapping
- OWASP Top 10
- A05:2021 - Security Misconfiguration
- OWASP ASVS
- V14.5.3 (L1)
Vulnerable vs. safe
Flagged by this check
config.addAllowedOrigin("*");Passes - the safe pattern
config.addAllowedOrigin("https://app.example.com");Why it matters & how to fix it
CORS is configured to allow any origin with "*" (CWE-942). Combined with allowed credentials this lets any website read authenticated responses on behalf of the victim. Replace the wildcard with an explicit allow-list of trusted origins, and never pair a wildcard origin with allowCredentials(true).
References
Rule ID integsec-java-permissive-cors-wildcard - engine: Opengrep - license: MIT - Copyright (c) IntegSec Inc.
TurboPentest runs this check automatically
Connect a GitHub repo and this check runs on every white-box pentest - AI-validated and reported with proof, from $99 per target.
Start a pentestRelated checks
- JavaScript / TypeScript - Insecure ConfigurationCORS Acao Wildcard Header
- JavaScript / TypeScript - Insecure ConfigurationCORS Wildcard Origin
- JavaScript / TypeScript - Insecure ConfigurationCORS Wildcard With Credentials
- JavaScript / TypeScript - Insecure ConfigurationCSRF Protection Disabled
- JavaScript / TypeScript - Insecure ConfigurationExpress Trust Proxy All
- JavaScript / TypeScript - Insecure ConfigurationExpress X Powered By Enabled