Risk Level | Number of Alerts |
---|---|
High
|
0
|
Medium
|
4
|
Low
|
2
|
Informational
|
6
|
False Positives:
|
0
|
Name | Risk Level | Number of Instances |
---|---|---|
CORS Misconfiguration | Medium | 2 |
Content Security Policy (CSP) Header Not Set | Medium | 5 |
Cross-Domain Misconfiguration | Medium | 1 |
Web Cache Deception | Medium | 1 |
In Page Banner Information Leak | Low | 5 |
Permissions Policy Header Not Set | Low | 5 |
Sec-Fetch-Dest Header is Missing | Informational | 4 |
Sec-Fetch-Mode Header is Missing | Informational | 4 |
Sec-Fetch-Site Header is Missing | Informational | 4 |
Sec-Fetch-User Header is Missing | Informational | 4 |
Storable and Cacheable Content | Informational | 5 |
User Agent Fuzzer | Informational | 12 |
Medium |
CORS Misconfiguration |
---|---|
Description |
This CORS misconfiguration could allow an attacker to perform AJAX queries to the vulnerable website from a malicious page loaded by the victim's user agent.
In order to perform authenticated AJAX queries, the server must specify the header "Access-Control-Allow-Credentials: true" and the "Access-Control-Allow-Origin" header must be set to null or the malicious page's domain. Even if this misconfiguration doesn't allow authenticated AJAX requests, unauthenticated sensitive content can still be accessed (e.g intranet websites).
A malicious page can belong to a malicious website but also a trusted website with flaws (e.g XSS, support of HTTP without TLS allowing code injection through MITM, etc).
|
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | |
Attack | origin: http://ay2Vsx81.com |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | |
Attack | origin: http://ay2Vsx81.com |
Evidence | |
Other Info | |
Instances | 2 |
Solution |
If a web resource contains sensitive information, the origin should be properly specified in the Access-Control-Allow-Origin header. Only trusted websites needing this resource should be specified in this header, with the most secured protocol supported.
|
Reference |
https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
https://portswigger.net/web-security/cors |
CWE Id | 942 |
WASC Id | 14 |
Plugin Id | 40040 |
Medium |
Content Security Policy (CSP) Header Not Set |
---|---|
Description |
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 — covered types are JavaScript, CSS, HTML frames, fonts, images and embeddable objects such as Java applets, ActiveX, audio and video files.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/favicon.ico |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
Instances | 5 |
Solution |
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
|
Reference |
https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Introducing_Content_Security_Policy
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/ |
CWE Id | 693 |
WASC Id | 15 |
Plugin Id | 10038 |
Medium |
Cross-Domain Misconfiguration |
---|---|
Description |
Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server.
|
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | |
Attack | |
Evidence | Access-Control-Allow-Origin: * |
Other Info | The CORS misconfiguration on the web server permits cross-domain read requests from arbitrary third party domains, using unauthenticated APIs on this domain. Web browser implementations do not permit arbitrary third parties to read the response from authenticated APIs, however. This reduces the risk somewhat. This misconfiguration could be used by an attacker to access data that is available in an unauthenticated manner, but which uses some other form of security, such as IP address white-listing. |
Instances | 1 |
Solution |
Ensure that sensitive data is not available in an unauthenticated manner (using IP address white-listing, for instance).
Configure the "Access-Control-Allow-Origin" HTTP header to a more restrictive set of domains, or remove all CORS headers entirely, to allow the web browser to enforce the Same Origin Policy (SOP) in a more restrictive manner.
|
Reference | https://vulncat.fortify.com/en/detail?id=desc.config.dotnet.html5_overly_permissive_cors_policy |
CWE Id | 264 |
WASC Id | 14 |
Plugin Id | 10098 |
Medium |
Web Cache Deception |
---|---|
Description |
Web cache deception may be possible. It may be possible for unauthorised user to view sensitive data on this page.
|
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | |
Attack | /test.css,/test.jpg,/test.js,/test.html,/test.gif,/test.png,/test.svg,/test.php,/test.txt,/test.pdf,/test.asp, |
Evidence | |
Other Info | Cached Authorised Response and Unauthorised Response are similar. |
Instances | 1 |
Solution |
It is strongly advised to refrain from classifying file types, such as images or stylesheets solely by their URL and file extension. Instead you should make sure that files are cached based on their Content-Type header.
|
Reference |
https://blogs.akamai.com/2017/03/on-web-cache-deception-attacks.html
https://www.netsparker.com/web-vulnerability-scanner/vulnerabilities/web-cache-deception/ |
CWE Id | |
WASC Id | |
Plugin Id | 40039 |
Low |
In Page Banner Information Leak |
---|---|
Description |
The server returned a version banner string in the response content. Such information leaks may allow attackers to further target specific issues impacting the product and version in use.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | |
Attack | |
Evidence | Tomcat/9.0.91 |
Other Info | There is a chance that the highlight in the finding is on a value in the headers, versus the actual matched string in the response body. |
URL | http://localhost:8080/favicon.ico |
Method | GET |
Parameter | |
Attack | |
Evidence | Tomcat/9.0.91 |
Other Info | There is a chance that the highlight in the finding is on a value in the headers, versus the actual matched string in the response body. |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | |
Attack | |
Evidence | Tomcat/9.0.91 |
Other Info | There is a chance that the highlight in the finding is on a value in the headers, versus the actual matched string in the response body. |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | |
Attack | |
Evidence | Tomcat/9.0.91 |
Other Info | There is a chance that the highlight in the finding is on a value in the headers, versus the actual matched string in the response body. |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | |
Attack | |
Evidence | Tomcat/9.0.91 |
Other Info | There is a chance that the highlight in the finding is on a value in the headers, versus the actual matched string in the response body. |
Instances | 5 |
Solution |
Configure the server to prevent such information leaks. For example:
Under Tomcat this is done via the "server" directive and implementation of custom error pages.
Under Apache this is done via the "ServerSignature" and "ServerTokens" directives.
|
Reference | https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/08-Testing_for_Error_Handling/ |
CWE Id | 200 |
WASC Id | 13 |
Plugin Id | 10009 |
Low |
Permissions Policy Header Not Set |
---|---|
Description |
Permissions Policy Header is an added layer of security that helps to restrict from unauthorized access or usage of browser/client features by web resources. This policy ensures the user privacy by limiting or specifying the features of the browsers can be used by the web resources. Permissions Policy provides a set of standard HTTP headers that allow website owners to limit which features of browsers can be used by the page such as camera, microphone, location, full screen etc.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/favicon.ico |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | |
Instances | 5 |
Solution |
Ensure that your web server, application server, load balancer, etc. is configured to set the Permissions-Policy header.
|
Reference |
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
https://developer.chrome.com/blog/feature-policy/ https://scotthelme.co.uk/a-new-security-header-feature-policy/ https://w3c.github.io/webappsec-feature-policy/ https://www.smashingmagazine.com/2018/12/feature-policy/ |
CWE Id | 693 |
WASC Id | 15 |
Plugin Id | 10063 |
Informational |
Sec-Fetch-Dest Header is Missing |
---|---|
Description |
Specifies how and where the data would be used. For instance, if the value is audio, then the requested resource must be audio data and not any other type of resource.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | Sec-Fetch-Dest |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | Sec-Fetch-Dest |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | Sec-Fetch-Dest |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | Sec-Fetch-Dest |
Attack | |
Evidence | |
Other Info | |
Instances | 4 |
Solution |
Ensure that Sec-Fetch-Dest header is included in request headers.
|
Reference | https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest |
CWE Id | 352 |
WASC Id | 9 |
Plugin Id | 90005 |
Informational |
Sec-Fetch-Mode Header is Missing |
---|---|
Description |
Allows to differentiate between requests for navigating between HTML pages and requests for loading resources like images, audio etc.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | Sec-Fetch-Mode |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | Sec-Fetch-Mode |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | Sec-Fetch-Mode |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | Sec-Fetch-Mode |
Attack | |
Evidence | |
Other Info | |
Instances | 4 |
Solution |
Ensure that Sec-Fetch-Mode header is included in request headers.
|
Reference | https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Mode |
CWE Id | 352 |
WASC Id | 9 |
Plugin Id | 90005 |
Informational |
Sec-Fetch-Site Header is Missing |
---|---|
Description |
Specifies the relationship between request initiator's origin and target's origin.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | Sec-Fetch-Site |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | Sec-Fetch-Site |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | Sec-Fetch-Site |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | Sec-Fetch-Site |
Attack | |
Evidence | |
Other Info | |
Instances | 4 |
Solution |
Ensure that Sec-Fetch-Site header is included in request headers.
|
Reference | https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Site |
CWE Id | 352 |
WASC Id | 9 |
Plugin Id | 90005 |
Informational |
Sec-Fetch-User Header is Missing |
---|---|
Description |
Specifies if a navigation request was initiated by a user.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | Sec-Fetch-User |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | Sec-Fetch-User |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | Sec-Fetch-User |
Attack | |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | Sec-Fetch-User |
Attack | |
Evidence | |
Other Info | |
Instances | 4 |
Solution |
Ensure that Sec-Fetch-User header is included in user initiated requests.
|
Reference | https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-User |
CWE Id | 352 |
WASC Id | 9 |
Plugin Id | 90005 |
Informational |
Storable and Cacheable Content |
---|---|
Description |
The response contents are storable by caching components such as proxy servers, and may be retrieved directly from the cache, rather than from the origin server by the caching servers, in response to similar requests from other users. If the response data is sensitive, personal or user-specific, this may result in sensitive information being leaked. In some cases, this may even result in a user gaining complete control of the session of another user, depending on the configuration of the caching components in use in their environment. This is primarily an issue where "shared" caching servers such as "proxy" caches are configured on the local network. This configuration is typically found in corporate or educational environments, for instance.
|
URL | http://localhost:8080/ |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234. |
URL | http://localhost:8080/favicon.ico |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234. |
URL | http://localhost:8080/robots.txt |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234. |
URL | http://localhost:8080/sitemap.xml |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234. |
URL | http://localhost:8080/tomcat-webapp-boilerplate/app |
Method | GET |
Parameter | |
Attack | |
Evidence | |
Other Info | In the absence of an explicitly specified caching lifetime directive in the response, a liberal lifetime heuristic of 1 year was assumed. This is permitted by rfc7234. |
Instances | 5 |
Solution |
Validate that the response does not contain sensitive, personal or user-specific information. If it does, consider the use of the following HTTP response headers, to limit, or prevent the content being stored and retrieved from the cache by another user:
Cache-Control: no-cache, no-store, must-revalidate, private
Pragma: no-cache
Expires: 0
This configuration directs both HTTP 1.0 and HTTP 1.1 compliant caching servers to not store the response, and to not retrieve the response (without validation) from the cache, in response to a similar request.
|
Reference |
https://datatracker.ietf.org/doc/html/rfc7234
https://datatracker.ietf.org/doc/html/rfc7231 https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html |
CWE Id | 524 |
WASC Id | 13 |
Plugin Id | 10049 |
Informational |
User Agent Fuzzer |
---|---|
Description |
Check for differences in response based on fuzzed User Agent (eg. mobile sites, access as a Search Engine Crawler). Compares the response statuscode and the hashcode of the response body with the original response.
|
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1) |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3739.0 Safari/537.36 Edg/75.0.109.0 |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36 |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:93.0) Gecko/20100101 Firefox/91.0 |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (compatible; Yahoo! Slurp; http://help.yahoo.com/help/us/ysearch/slurp) |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (iPhone; CPU iPhone OS 8_0_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12A366 Safari/600.1.4 |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | Mozilla/5.0 (iPhone; U; CPU iPhone OS 3_0 like Mac OS X; en-us) AppleWebKit/528.18 (KHTML, like Gecko) Version/4.0 Mobile/7A341 Safari/528.16 |
Evidence | |
Other Info | |
URL | http://localhost:8080/tomcat-webapp-boilerplate |
Method | GET |
Parameter | Header User-Agent |
Attack | msnbot/1.1 (+http://search.msn.com/msnbot.htm) |
Evidence | |
Other Info | |
Instances | 12 |
Solution | |
Reference | https://owasp.org/wstg |
CWE Id | |
WASC Id | |
Plugin Id | 10104 |