1db84cc1-8fe3-46bd-a202-51523485d34f
1db84cc1-8fe3-46bd-a202-51523485d34f
Vulnerability Scan
Report
Prepared By
HostedScan Security
hostedscan.com
HostedScan Security Vulnerability Scan Report
Overview
1 Executive Summary 3
2 Vulnerabilities By Target 4
4 Glossary 16
hostedscan.com 2
Executive Summary Vulnerability Scan Report
1 Executive Summary
Vulnerability scans were conducted on select servers, networks, websites, and applications. This report contains the
discovered potential vulnerabilities from these scans. Vulnerabilities have been classified by severity. Higher severity
indicates a greater risk of a data breach, loss of integrity, or availability of the targets.
0 0 5 3 0
63% 38%
Vulnerability Categories
8
Passive Web Application Vulnerabilities
hostedscan.com 3
Vulnerabilities By Target Vulnerability Scan Report
2 Vulnerabilities By Target
This section contains the vulnerability findings for each scanned target. Prioritization should be given to the
targets with the highest severity vulnerabilities. However, it is important to take into account the purpose of each
system and consider the potential impact a breach or an outage would have for the particular target.
https://petstore.octoperf.com/actions/Catalog.action 0 0 5 3 0
hostedscan.com 4
Vulnerabilities By Target | https://petstore.octoperf.com/actions/Catalog.action Vulnerability Scan Report
https://petstore.octoperf.com/actions/Catalog.action
Total Risks
0 0 5 3 0
63% 38%
Content Security Policy (CSP) Header Not Set Medium 0 days ago 0 days ago
hostedscan.com 5
Passive Web Application Vulnerabilities Vulnerability Scan Report
0 0 5 3 0
63% 38%
hostedscan.com 6
Passive Web Application Vulnerabilities | Absence of Anti-CSRF Tokens Vulnerability Scan Report
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.
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.
hostedscan.com 7
Passive Web Application Vulnerabilities | Absence of Anti-CSRF Tokens Vulnerability Scan Report
hostedscan.com 8
Passive Web Application Vulnerabilities | Missing Anti-clickjacking Header Vulnerability Scan Report
Description
The response does not protect against 'ClickJacking' attacks. It should include either Content-Security-Policy with 'frame-ancestors'
directive or X-Frame-Options.
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 72)
uri: https://petstore.octoperf.com/
method: GET
param: x-frame-options
References
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options
hostedscan.com 9
Passive Web Application Vulnerabilities | Referer Exposes Session ID Vulnerability Scan Report
Description
A hyperlink pointing to another host name was found. As session ID URL rewrite is used, it may be disclosed in referer header to external
hosts.
Solution
This is a risk if the session ID is sensitive and the hyperlink refers to an external or third party host. For secure content, put session ID in
secured session cookie.
Instances (1 of 9)
uri: https://petstore.octoperf.com/actions/Account.action;jsessionid=A48BDC202076101C50D611BAFD0C9979?signonForm
method: GET
evidence: octoperf.com
References
https://seclists.org/webappsec/2002/q4/111
hostedscan.com 10
Passive Web Application Vulnerabilities | Session ID in URL Rewrite Vulnerability Scan Report
Description
URL rewrite is used to track user session ID. The session ID may be disclosed via cross-site referer header. In addition, the session ID
might be stored in browser history or server logs.
Solution
For secure content, put session ID in a cookie. To be even more secure consider using a combination of cookie and URL rewrite.
Instances (1 of 9)
uri: https://petstore.octoperf.com/actions/Account.action;jsessionid=A48BDC202076101C50D611BAFD0C9979?signonForm
method: GET
evidence: jsessionid=A48BDC202076101C50D611BAFD0C9979
References
https://seclists.org/webappsec/2002/q4/111
hostedscan.com 11
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 75)
uri: https://petstore.octoperf.com/
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 12
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 78)
uri: https://petstore.octoperf.com/
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 13
Passive Web Application Vulnerabilities | Cookie Without Secure Flag Vulnerability Scan Report
Description
A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.
Solution
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel.
Ensure that the secure flag is set for cookies containing such sensitive information.
Instances (1 of 10)
uri: https://petstore.octoperf.com/actions/Account.action?editAccountForm
method: GET
param: JSESSIONID
evidence: Set-Cookie: JSESSIONID
References
https://owasp.org/www-project-web-security-testing-guide/v41/4-Web_Application_Security_Testing/06-Session_Management_Testing/02-
Testing_for_Cookies_Attributes.html
hostedscan.com 14
Passive Web Application Vulnerabilities | Cookie without SameSite Attribute Vulnerability Scan Report
Description
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.
Solution
Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.
Instances (1 of 10)
uri: https://petstore.octoperf.com/actions/Account.action?editAccountForm
method: GET
param: JSESSIONID
evidence: Set-Cookie: JSESSIONID
References
https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site
hostedscan.com 15
Glossary Vulnerability Scan Report
4 Glossary
Accepted Vulnerability Vulnerability
An accepted vulnerability is one which has been manually A weakness in the computational logic (e.g., code) found
reviewed and classified as acceptable to not fix at this in software and hardware components that, when
time, such as a false positive scan result or an intentional exploited, results in a negative impact to confidentiality,
part of the system's architecture. integrity, or availability. Mitigation of the vulnerabilities in
this context typically involves coding changes, but could
Fully Qualified Domain Name (FQDN) also include specification changes or even specification
A fully qualified domain name is a complete domain name deprecations (e.g., removal of affected protocols or
for a specific website or service on the internet. This functionality in their entirety).
includes not only the website or service name, but also the
top-level domain name, such as .com, .org, .net, etc. For Target
example, 'www.example.com' is an FQDN. A target represents target is a single URL, IP address, or
fully qualified domain name (FQDN) that was scanned.
Passive Web Application Vulnerabilities
The OWASP ZAP Passive Web Application scan crawls the Severity
pages of a website or web application. The passive scan Severity represents the estimated impact potential of a
inspects each page as well as the requests and responses particular vulnerability. Severity is divided into 5
sent between the server. The passive scan checks for categories: Critical, High, Medium, Low and Accepted.
vulnerabilities such as cross-domain misconfigurations,
insecure cookies, vulnerable Javascript dependencies, CVSS Score
and more. The CVSS 3.0 score is a global standard for evaluating
vulnerabilities with a 0 to 10 scale. CVSS maps to threat
levels:
0.1 - 3.9 = Low
4.0 - 6.9 = Medium
7.0 - 8.9 = High
9.0 - 10.0 = Critical
hostedscan.com 16
This report was prepared using
HostedScan Security ®
For more information, visit hostedscan.com
Founded in Seattle, Washington in 2019, HostedScan, LLC. is
dedicated to making continuous vulnerability scanning and risk
management much more easily accessible to more businesses.
HostedScan, LLC.
2212 Queen Anne Ave N
Suite #521 Terms & Policies
Seattle, WA 98109 [email protected]
hostedscan.com 17