+ ZAP Scanning Report
+
+ ZAP Scanning Report
+ | Risk Level | +Number of Alerts | +
|---|---|
|
+ High
+ |
+
+ 0
+ |
+
|
+ Medium
+ |
+
+ 4
+ |
+
|
+ Low
+ |
+
+ 5
+ |
+
|
+ Informational
+ |
+
+ 4
+ |
+
|
+ False Positives:
+ |
+
+ 0
+ |
+
| Name | +Risk Level | +Number of Instances | +
|---|---|---|
| Absence of Anti-CSRF Tokens | +Medium | +4 | +
| Content Security Policy (CSP) Header Not Set | +Medium | +9 | +
| Missing Anti-clickjacking Header | +Medium | +9 | +
| Sub Resource Integrity Attribute Missing | +Medium | +10 | +
| Application Error Disclosure | +Low | +1 | +
| Cross-Domain JavaScript Source File Inclusion | +Low | +12 | +
| Information Disclosure - Debug Error Messages | +Low | +1 | +
| Permissions Policy Header Not Set | +Low | +10 | +
| X-Content-Type-Options Header Missing | +Low | +11 | +
| Information Disclosure - Suspicious Comments | +Informational | +1 | +
| Non-Storable Content | +Informational | +1 | +
| Storable and Cacheable Content | +Informational | +10 | +
| User Controllable HTML Element Attribute (Potential XSS) | +Informational | +6 | +
|
+ Medium |
+ Absence of Anti-CSRF Tokens | +
|---|---|
| Description | +
+ No Anti-CSRF tokens were found in a HTML submission form.
+ + + A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.
+ + + CSRF attacks are effective in a number of situations, including:
+ + + * The victim has an active session on the target site.
+ + + * The victim is authenticated via HTTP auth on the target site.
+ + + * The victim is on the same local network as the target site.
+ + + CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.
+
+ |
+
| + | |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<form action="/owners" method="get" + class="form-horizontal" id="search-owner-form"> | +
| Other Info | +No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: "lastName" ]. | +
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<form class="form-horizontal" id="add-owner-form" method="post"> | +
| Other Info | +No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: "address" "city" "firstName" "lastName" "telephone" ]. | +
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<form action="/owners" method="get" + class="form-horizontal" id="search-owner-form"> | +
| Other Info | +No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: "lastName" ]. | +
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<form class="form-horizontal" id="add-owner-form" method="post"> | +
| Other Info | +No known Anti-CSRF token [anticsrf, CSRFToken, __RequestVerificationToken, csrfmiddlewaretoken, authenticity_token, OWASP_CSRFTOKEN, anoncsrf, csrf_token, _csrf, _csrfSecret, __csrf_magic, CSRF, _token, _csrf_token] was found in the following HTML form: [Form 1: "address" "city" "firstName" "lastName" "telephone" ]. | +
| Instances | +4 | +
| Solution | +
+ Phase: Architecture and Design
+ + + Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
+ + + For example, use anti-CSRF packages such as the OWASP CSRFGuard.
+ + + Phase: Implementation
+ + + Ensure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.
+ + + Phase: Architecture and Design
+ + + Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
+ + + Note that this can be bypassed using XSS.
+ + + Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
+ + + Note that this can be bypassed using XSS.
+ + + Use the ESAPI Session Management control.
+ + + This control includes a component for CSRF.
+ + + Do not use the GET method for any request that triggers a state change.
+ + + Phase: Implementation
+ + + Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
+
+ |
+
| Reference | +
+ https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html
+ + + https://cwe.mitre.org/data/definitions/352.html + + |
+
| CWE Id | +352 | +
| WASC Id | +9 | +
| Plugin Id | +10202 | +
|
+ 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/ | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html?page=1 | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html?page=2 | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| Instances | +9 | +
| 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 |
+ Missing Anti-clickjacking Header | +
|---|---|
| Description | +
+ The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against 'ClickJacking' attacks.
+
+ |
+
| + | |
| URL | +http://localhost:8080 | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/ | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html?page=1 | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html?page=2 | +
| Method | +GET | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +x-frame-options | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| Instances | +9 | +
| 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.
+
+ |
+
| Reference | ++ https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options + + | +
| CWE Id | +1021 | +
| WASC Id | +15 | +
| Plugin Id | +10020 | +
|
+ Medium |
+ Sub Resource Integrity Attribute Missing | +
|---|---|
| Description | +
+ The integrity attribute is missing on a script or link tag served by an external server. The integrity tag prevents an attacker who have gained access to this server from injecting a malicious content.
+
+ |
+
| + | |
| URL | +http://localhost:8080 | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080 | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/ | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/ | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| Instances | +10 | +
| Solution | +
+ Provide a valid integrity attribute to the tag.
+
+ |
+
| Reference | ++ https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity + + | +
| CWE Id | +345 | +
| WASC Id | +15 | +
| Plugin Id | +90003 | +
|
+ Low |
+ Application Error Disclosure | +
|---|---|
| Description | +
+ This page contains an error/warning message that may disclose sensitive information like the location of the file that produced the unhandled exception. This information can be used to launch further attacks against the web application. The alert could be a false positive if the error message is found inside a documentation page.
+
+ |
+
| + | |
| URL | +http://localhost:8080/oups | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +HTTP/1.1 500 | +
| Other Info | ++ |
| Instances | +1 | +
| Solution | +
+ Review the source code of this page. Implement custom error pages. Consider implementing a mechanism to provide a unique error reference/identifier to the client (browser) while logging the details on the server side and not exposing them to the user.
+
+ |
+
| Reference | ++ |
| CWE Id | +200 | +
| WASC Id | +13 | +
| Plugin Id | +90022 | +
|
+ Low |
+ Cross-Domain JavaScript Source File Inclusion | +
|---|---|
| Description | +
+ The page includes one or more script files from a third-party domain.
+
+ |
+
| + | |
| URL | +http://localhost:8080 | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080 | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/respond/1.4.2/respond.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/ | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/ | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/respond/1.4.2/respond.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/respond/1.4.2/respond.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/respond/1.4.2/respond.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | +https://oss.maxcdn.com/respond/1.4.2/respond.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script> | +
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +https://oss.maxcdn.com/respond/1.4.2/respond.min.js | +
| Attack | ++ |
| Evidence | +<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script> | +
| Other Info | ++ |
| Instances | +12 | +
| Solution | +
+ Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.
+
+ |
+
| Reference | ++ |
| CWE Id | +829 | +
| WASC Id | +15 | +
| Plugin Id | +10017 | +
|
+ Low |
+ Information Disclosure - Debug Error Messages | +
|---|---|
| Description | +
+ The response appeared to contain common error messages returned by platforms such as ASP.NET, and Web-servers such as IIS and Apache. You can configure the list of common debug messages.
+
+ |
+
| + | |
| URL | +http://localhost:8080/oups | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +Internal Server Error | +
| Other Info | ++ |
| Instances | +1 | +
| Solution | +
+ Disable debugging messages before pushing to production.
+
+ |
+
| Reference | ++ |
| CWE Id | +200 | +
| WASC Id | +13 | +
| Plugin Id | +10023 | +
|
+ 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/ | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html?page=1 | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/vets.html?page=2 | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/webjars/bootstrap/5.3.3/dist/js/bootstrap.bundle.min.js | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | ++ |
| Other Info | ++ |
| Instances | +10 | +
| 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 | +
|
+ Low |
+ X-Content-Type-Options Header Missing | +
|---|---|
| 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.
+
+ |
+
| + | |
| URL | +http://localhost:8080 | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/ | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/owners/find | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/owners/new | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/resources/css/petclinic.css | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/resources/images/favicon.png | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/resources/images/pets.png | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/resources/images/spring-logo.svg | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/webjars/bootstrap/5.3.3/dist/js/bootstrap.bundle.min.js | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| URL | +http://localhost:8080/webjars/font-awesome/4.7.0/css/font-awesome.min.css | +
| Method | +GET | +
| Parameter | +x-content-type-options | +
| Attack | ++ |
| Evidence | ++ |
| 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. | +
| Instances | +11 | +
| 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.
+
+ |
+
| 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 + + |
+
| CWE Id | +693 | +
| WASC Id | +15 | +
| Plugin Id | +10021 | +
|
+ Informational |
+ Information Disclosure - Suspicious Comments | +
|---|---|
| Description | +
+ The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.
+
+ |
+
| + | |
| URL | +http://localhost:8080/webjars/bootstrap/5.3.3/dist/js/bootstrap.bundle.min.js | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +select | +
| Other Info | +The following pattern was used: \bSELECT\b and was detected in the element starting with: "!function(t,e){"object"==typeof exports&&"undefined"!=typeof module?module.exports=e():"function"==typeof define&&define.amd?def", see evidence field for the suspicious comment/snippet. | +
| Instances | +1 | +
| Solution | +
+ Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.
+
+ |
+
| Reference | ++ |
| CWE Id | +200 | +
| WASC Id | +13 | +
| Plugin Id | +10027 | +
|
+ Informational |
+ Non-Storable Content | +
|---|---|
| Description | +
+ The response contents are not storable by caching components such as proxy servers. If the response does not contain sensitive, personal or user-specific information, it may benefit from being stored and cached, to improve performance.
+
+ |
+
| + | |
| URL | +http://localhost:8080/oups | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +500 | +
| Other Info | ++ |
| Instances | +1 | +
| Solution | +
+ The content may be marked as storable by ensuring that the following conditions are satisfied:
+ + + The request method must be understood by the cache and defined as being cacheable ("GET", "HEAD", and "POST" are currently defined as cacheable)
+ + + The response status code must be understood by the cache (one of the 1XX, 2XX, 3XX, 4XX, or 5XX response classes are generally understood)
+ + + The "no-store" cache directive must not appear in the request or response header fields
+ + + For caching by "shared" caches such as "proxy" caches, the "private" response directive must not appear in the response
+ + + For caching by "shared" caches such as "proxy" caches, the "Authorization" header field must not appear in the request, unless the response explicitly allows it (using one of the "must-revalidate", "public", or "s-maxage" Cache-Control response directives)
+ + + In addition to the conditions above, at least one of the following conditions must also be satisfied by the response:
+ + + It must contain an "Expires" header field
+ + + It must contain a "max-age" response directive
+ + + For "shared" caches such as "proxy" caches, it must contain a "s-maxage" response directive
+ + + It must contain a "Cache Control Extension" that allows it to be cached
+ + + It must have a status code that is defined as cacheable by default (200, 203, 204, 206, 300, 301, 404, 405, 410, 414, 501).
+
+ |
+
| 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 |
+ 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/ | +
| 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/owners/find | +
| 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/resources/css/petclinic.css | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +max-age=43200 | +
| Other Info | ++ |
| URL | +http://localhost:8080/resources/images/favicon.png | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +max-age=43200 | +
| Other Info | ++ |
| URL | +http://localhost:8080/resources/images/pets.png | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +max-age=43200 | +
| Other Info | ++ |
| URL | +http://localhost:8080/resources/images/spring-logo.svg | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +max-age=43200 | +
| Other Info | ++ |
| 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/webjars/font-awesome/4.7.0/css/font-awesome.min.css | +
| Method | +GET | +
| Parameter | ++ |
| Attack | ++ |
| Evidence | +max-age=43200 | +
| Other Info | ++ |
| Instances | +10 | +
| 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 Controllable HTML Element Attribute (Potential XSS) | +
|---|---|
| Description | +
+ This check looks at user-supplied input in query string parameters and POST data to identify where certain HTML attribute values might be controlled. This provides hot-spot detection for XSS (cross-site scripting) that will require further review by a security analyst to determine exploitability.
+
+ |
+
| + | |
| URL | +http://localhost:8080/owners?lastName=ZAP | +
| Method | +GET | +
| Parameter | +lastName | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | +User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL: + +http://localhost:8080/owners?lastName=ZAP + +appears to include user input in: + +a(n) [input] tag [value] attribute + +The user input found was: +lastName=ZAP + +The user-controlled value was: +zap | +
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +address | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | +User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL: + +http://localhost:8080/owners/new + +appears to include user input in: + +a(n) [input] tag [value] attribute + +The user input found was: +address=688 Zaproxy Ridge + +The user-controlled value was: +688 zaproxy ridge | +
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +city | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | +User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL: + +http://localhost:8080/owners/new + +appears to include user input in: + +a(n) [input] tag [value] attribute + +The user input found was: +city=East Romaineburgh + +The user-controlled value was: +east romaineburgh | +
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +firstName | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | +User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL: + +http://localhost:8080/owners/new + +appears to include user input in: + +a(n) [input] tag [value] attribute + +The user input found was: +firstName=ZAP + +The user-controlled value was: +zap | +
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +lastName | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | +User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL: + +http://localhost:8080/owners/new + +appears to include user input in: + +a(n) [input] tag [value] attribute + +The user input found was: +lastName=ZAP + +The user-controlled value was: +zap | +
| URL | +http://localhost:8080/owners/new | +
| Method | +POST | +
| Parameter | +telephone | +
| Attack | ++ |
| Evidence | ++ |
| Other Info | +User-controlled HTML attribute values were found. Try injecting special characters to see if XSS might be possible. The page at the following URL: + +http://localhost:8080/owners/new + +appears to include user input in: + +a(n) [input] tag [value] attribute + +The user input found was: +telephone=ZAP + +The user-controlled value was: +zap | +
| Instances | +6 | +
| Solution | +
+ Validate all input and sanitize output it before writing to any HTML attributes.
+
+ |
+
| Reference | ++ https://cheatsheetseries.owasp.org/cheatsheets/Input_Validation_Cheat_Sheet.html + + | +
| CWE Id | +20 | +
| WASC Id | +20 | +
| Plugin Id | +10031 | +
