Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks. These attacks are used for everything from data theft to site defacement or distribution of malware. CSP provides a set of standard HTTP headers that allow website owners to declare approved sources of content that browsers should be allowed to load on that page \u2014 covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
", "instances":[ { "id": "1", "uri": "http://127.0.0.1:8781/", "nodeName": "http:\/\/127.0.0.1:8781\/", "method": "GET", "param": "", "attack": "", "evidence": "", "otherinfo": "" } ], "count": "1", "systemic": true, "solution": "Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
", "otherinfo": "", "reference": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
https://www.w3.org/TR/CSP/
https://w3c.github.io/webappsec-csp/
https://web.dev/articles/csp
https://caniuse.com/#feat=contentsecuritypolicy
https://content-security-policy.com/
", "cweid": "693", "wascid": "15", "sourceid": "1" }, { "pluginid": "10020", "alertRef": "10020-1", "alert": "Missing Anti-clickjacking Header", "name": "Missing Anti-clickjacking Header", "riskcode": "2", "confidence": "2", "riskdesc": "Medium (Medium)", "desc": "The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options.
", "instances":[ { "id": "0", "uri": "http://127.0.0.1:8781/", "nodeName": "http:\/\/127.0.0.1:8781\/", "method": "GET", "param": "x-frame-options", "attack": "", "evidence": "", "otherinfo": "" } ], "count": "1", "systemic": true, "solution": "Modern Web browsers support the Content-Security-Policy and X-Frame-Options HTTP headers. Ensure one of them is set on all web pages returned by your site/app.
If you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. Alternatively consider implementing Content Security Policy's \"frame-ancestors\" directive.
", "otherinfo": "", "reference": "https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options
", "cweid": "1021", "wascid": "15", "sourceid": "1" }, { "pluginid": "10010", "alertRef": "10010", "alert": "Cookie No HttpOnly Flag", "name": "Cookie No HttpOnly Flag", "riskcode": "1", "confidence": "2", "riskdesc": "Low (Medium)", "desc": "A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.
", "instances":[ { "id": "2", "uri": "http://127.0.0.1:8781/", "nodeName": "http:\/\/127.0.0.1:8781\/", "method": "GET", "param": "synthetic_session", "attack": "", "evidence": "Set-Cookie: synthetic_session", "otherinfo": "" } ], "count": "1", "systemic": true, "solution": "Ensure that the HttpOnly flag is set for all cookies.
", "otherinfo": "", "reference": "https://owasp.org/www-community/HttpOnly
", "cweid": "1004", "wascid": "13", "sourceid": "1" }, { "pluginid": "10054", "alertRef": "10054-1", "alert": "Cookie without SameSite Attribute", "name": "Cookie without SameSite Attribute", "riskcode": "1", "confidence": "2", "riskdesc": "Low (Medium)", "desc": "A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.
", "instances":[ { "id": "3", "uri": "http://127.0.0.1:8781/", "nodeName": "http:\/\/127.0.0.1:8781\/", "method": "GET", "param": "synthetic_session", "attack": "", "evidence": "Set-Cookie: synthetic_session", "otherinfo": "" } ], "count": "1", "systemic": true, "solution": "Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.
", "otherinfo": "", "reference": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cookie-same-site
", "cweid": "1275", "wascid": "13", "sourceid": "1" }, { "pluginid": "10036", "alertRef": "10036-2", "alert": "Server Leaks Version Information via \"Server\" HTTP Response Header Field", "name": "Server Leaks Version Information via \"Server\" HTTP Response Header Field", "riskcode": "1", "confidence": "3", "riskdesc": "Low (High)", "desc": "The web/application server is leaking version information via the \"Server\" HTTP response header. Access to such information may facilitate attackers identifying other vulnerabilities your web/application server is subject to.
", "instances":[ { "id": "4", "uri": "http://127.0.0.1:8781/", "nodeName": "http:\/\/127.0.0.1:8781\/", "method": "GET", "param": "", "attack": "", "evidence": "BaseHTTP/0.6 Python/3.11.4", "otherinfo": "" } ], "count": "1", "systemic": true, "solution": "Ensure that your web server, application server, load balancer, etc. is configured to suppress the \"Server\" header or provide generic details.
", "otherinfo": "", "reference": "https://httpd.apache.org/docs/current/mod/core.html#servertokens
https://learn.microsoft.com/en-us/previous-versions/msp-n-p/ff648552(v=pandp.10)
https://www.troyhunt.com/shhh-dont-let-your-response-headers/
", "cweid": "497", "wascid": "13", "sourceid": "1" }, { "pluginid": "10021", "alertRef": "10021", "alert": "X-Content-Type-Options Header Missing", "name": "X-Content-Type-Options Header Missing", "riskcode": "1", "confidence": "2", "riskdesc": "Low (Medium)", "desc": "The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.
", "instances":[ { "id": "5", "uri": "http://127.0.0.1:8781/", "nodeName": "http:\/\/127.0.0.1:8781\/", "method": "GET", "param": "x-content-type-options", "attack": "", "evidence": "", "otherinfo": "This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.\nAt \"High\" threshold this scan rule will not alert on client or server error responses." } ], "count": "1", "systemic": true, "solution": "Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.
", "otherinfo": "This issue still applies to error type pages (401, 403, 500, etc.) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.
At \"High\" threshold this scan rule will not alert on client or server error responses.
", "reference": "https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/compatibility/gg622941(v=vs.85)
https://owasp.org/www-community/Security_Headers
", "cweid": "693", "wascid": "15", "sourceid": "1" } ] } ], "sequences":[ ] }