The application has unnsafe configurations regarding the Content-Security-Policy header. This may be because:
- Header is missing from server responses.
- The header has not defined mandatory security policies.
- Defined security policies contain insecure values.
- Embed content, scripts, blobs or images from potentially malicious sources.
- Make possible to carry attacks like Cross-Site Scripting, Cross-Site Leaks, among others.
Set the Content-Security-Policy header in the server responses and configure it in a secure way.
Unauthorized attacker from Internet.
Expected Remediation Time
Default score using CVSS 3.1. It may change depending on the context of the src.
- Attack vector: N
- Attack complexity: H
- Privileges required: N
- User interaction: R
- Scope: U
- Confidentiality: L
- Integrity: L
- Availability: N
- Exploit code madurity: P
- Remediation level: O
- Report confidence: C
- Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C
- Base: 4.2
- Temporal: 3.8
- Base: Medium
- Temporal: Low
- 062.Define standard configurations
- 117.Do not interpret HTML code
- 175.Protect pages from clickjacking
- 349.Include HTTP security headers
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.