ZAP Scanning Report

Alerts

1. Risk=Baixo, Confidence=Médio (1)

   1. http://localhost:8082 (1)

      1. X-Content-Type-Options Header Missing (1)

         1. GET http://localhost:8082/api/v1/products/category/LANCHE?page=0&size=10

            Alert tags	OWASP_2021_A05 OWASP_2017_A06
            Alert description	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.
            Other info	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.
            Request	Request line and header section (311 bytes) GET http://localhost:8082/api/v1/products/category/LANCHE?page=0&size=10 HTTP/1.1 User-Agent: PostmanRuntime/7.28.1 Accept: */* Postman-Token: 00590b6f-ac34-499b-95c1-66d3cfcd856c Connection: keep-alive Referer: http://localhost:8082/api/v1/products/category/LANCHE?page=0&size=10 host: localhost:8082 Request body (0 bytes)
            Response	Status line and header section (154 bytes) HTTP/1.1 200 Content-Type: application/json Date: Tue, 12 Mar 2024 01:11:02 GMT Keep-Alive: timeout=60 Connection: keep-alive content-length: 170 Response body (170 bytes) {"code":200,"body":[{"sku":"65efab871c5ba5178ce3e871","title":"X salada","category":"LANCHE","description":"test","price":12.1,"image":"test"}],"hasNext":false,"total":1}
            Parameter	x-content-type-options
            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.