Insecure or unset HTTP headers - CORS

Description

The cross-domain policy includes wildcards, accepting any domain as valid for sharing resources.

Impact

Include resources from untrusted origins.

Recommendation

Remove the wildcard (*) and define explicitly the trusted origins for the application resources.

Threat

Unauthorized attacker from the Internet.

Expected Remediation Time

⌚ minutes.

Score

Default score using CVSS 3.1. It may change depending on the context of the src.

Base

• Attack vector: N
• Attack complexity: H
• Privileges required: N
• User interaction: R
• Scope: U
• Confidentiality: N
• Integrity: L
• Availability: N

Temporal

• Exploit code madurity: P
• Remediation level: U
• Report confidence: C

Result

• Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:U/RC:C
• Score:
  • Base: 3.1
  • Temporal: 3.0
• Severity:
  • Base: Low
  • Temporal: Low

Requirements

• 062.Define standard configurations
• 266.Disable insecure functionalities
• 349.Include HTTP security headers

Fixes

• Elixir
• Scala
• Python
• Ruby
• Go
• Dart
• Java
• C-Sharp
• TypeScript

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.