Professional Documents
Culture Documents
owasp zap hostedscan report 2024-04-30
owasp zap hostedscan report 2024-04-30
Vulnerability Scan
Report
prepared by
HostedScan Security
hostedscan.com
HostedScan Security Vulnerability Scan Report
Overview
1 Executive Summary 3
2 Risks By Target 4
4 Glossary 15
hostedscan.com 2
Executive Summary Vulnerability Scan Report
1 Executive Summary
Vulnerability scans were conducted on selected servers, networks, websites, and applications. This report contains
the discovered potential risks from these scans. Risks have been classified into categories according to the level of
threat and degree of potential harm they may pose.
0 0 4 4 0
50% 50%
Vulnerability Categories
8
Passive Web Application Vulnerabilities
hostedscan.com 3
Risks By Target Vulnerability Scan Report
2 Risks By Target
This section contains the vulnerability findings for each target that was scanned. Prioritize the most vulnerable assets
first.
41.66.249.148 0 0 4 4 0
hostedscan.com 4
Risks By Target | 41.66.249.148 Vulnerability Scan Report
Target
41.66.249.148
Total Risks
0 0 4 4 0
50% 50%
Passive Web Application Vulnerabilities Threat Level First Detected Last Detected
Content Security Policy (CSP) Header Not Set Medium 0 days ago 0 days ago
Server Leaks Information via "X-Powered-By" Low 0 days ago 0 days ago
HTTP Response Header Field(s)
Server Leaks Version Information via "Server" Low 0 days ago 0 days ago
HTTP Response Header Field
hostedscan.com 5
Passive Web Application Vulnerabilities Vulnerability Scan Report
0 0 4 4 0
50% 50%
Server Leaks Version Information via "Server" HTTP Response Header Low 1 0
Field
hostedscan.com 6
Passive Web Application Vulnerabilities | Cross-Domain Misconfiguration Vulnerability Scan Report
Cross-Domain Misconfiguration
Medium
Description
Web browser data loading may be possible, due to a Cross Origin Resource Sharing (CORS) misconfiguration on the web server
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.
Instances (1 of 14)
uri: https://41.66.249.148/api/Auth/
method: POST
evidence: Access-Control-Allow-Origin: *
otherinfo: 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.
References
https://vulncat.fortify.com/en/detail?id=desc.config.dotnet.html5_overly_permissive_cors_policy
hostedscan.com 7
Passive Web Application Vulnerabilities | Missing Anti-clickjacking Header Vulnerability Scan Report
Description
The response does not include either Content-Security-Policy with 'frame-ancestors' directive or X-Frame-Options to protect against
'ClickJacking' attacks.
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.
Instances (1 of 3)
uri: https://41.66.249.148/
method: GET
param: x-frame-options
References
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
hostedscan.com 8
Passive Web Application Vulnerabilities | Content Security Policy (CSP) Header Not Set Vulnerability Scan Report
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.
Solution
Ensure that your web server, application server, load balancer, etc. is configured to set the Content-Security-Policy header.
Instances (1 of 3)
uri: https://41.66.249.148/
method: GET
References
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/
hostedscan.com 9
Passive Web Application Vulnerabilities | Vulnerable JS Library Vulnerability Scan Report
Vulnerable JS Library
Medium
Description
The identified library jquery.datatables, version 1.10.18 is vulnerable.
Solution
Please upgrade to the latest version of jquery.datatables.
Instances (1 of 4)
uri: https://41.66.249.148/FlexibankUI/scripts/datatables.min.js
method: GET
evidence: n.version="1.10.18";n.settings=[];n.models={};n.models.oSearch
otherinfo: CVE-2020-28458 CVE-2021-23445
References
https://github.com/advisories/GHSA-m7j4-fhg6-xf5v
https://cdn.datatables.net/1.11.3/
https://github.com/advisories/GHSA-h73q-5wmj-q8pj
https://cdn.datatables.net/1.10.23/
https://github.com/DataTables/DataTablesSrc/commit/a51cbe99fd3d02aa5582f97d4af1615d11a1ea03
https://github.com/DataTables/Dist-DataTables/commit/59a8d3f8a3c1138ab08704e783bc52bfe88d7c9b
https://cdn.datatables.net/1.10.22/
hostedscan.com 10
Passive Web Application Vulnerabilities | X-Content-Type-Options Header Missing Vulnerability Scan Report
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.
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.
Instances (1 of 36)
uri: https://41.66.249.148/
method: GET
param: x-content-type-options
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.
References
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
hostedscan.com 11
Passive Web Application Vulnerabilities | Server Leaks Information via "X-Powered-By" HTTP Response Header Field(s) Vulnerability Sca
Description
The web/application server is leaking information via one or more "X-Powered-By" HTTP response headers. Access to such information
may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such
components may be subject to.
Solution
Ensure that your web server, application server, load balancer, etc. is configured to suppress "X-Powered-By" headers.
Instances (1 of 42)
uri: https://41.66.249.148/
method: GET
evidence: X-Powered-By: ASP.NET
References
https://owasp.org/www-project-web-security-testing-guide/v42/4-Web_Application_Security_Testing/01-Information_Gathering/08-
Fingerprint_Web_Application_Framework
https://www.troyhunt.com/2012/02/shhh-dont-let-your-response-headers.html
hostedscan.com 12
Passive Web Application Vulnerabilities | Server Leaks Version Information via "Server" HTTP Response Header Field Vulnerability Scan
Server Leaks Version Information via "Server" HTTP Response Header Field
Low
Description
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.
Solution
Ensure that your web server, application server, load balancer, etc. is configured to suppress the "Server" header or provide generic
details.
Instances (1 of 42)
uri: https://41.66.249.148/
method: GET
evidence: Microsoft-IIS/8.5
References
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/
hostedscan.com 13
Passive Web Application Vulnerabilities | Strict-Transport-Security Header Not Set Vulnerability Scan Report
Description
HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents
(such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF
standards track protocol and is specified in RFC 6797.
Solution
Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security.
Instances (1 of 2)
uri: https://41.66.249.148/api/Styles/
method: GET
References
https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html
https://owasp.org/www-community/Security_Headers
https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
https://caniuse.com/stricttransportsecurity
https://datatracker.ietf.org/doc/html/rfc6797
hostedscan.com 14
Glossary Vulnerability Scan Report
4 Glossary
Accepted Risk Risk
An accepted risk is one which has been manually A risk is a finding from a vulnerability scan. Each risk is a
reviewed and classified as acceptable to not fix at this potential security issue that needs review. Risks are
time, such as a false positive or an intentional part of the assigned a threat level which represents the potential
system's architecture. severity.
hostedscan.com 15
This report was prepared using
HostedScan Security ®
For more information, visit hostedscan.com
HostedScan, LLC.
hostedscan.com 16