Website Scanner-Https WWW - Demoblaze.com-20250506-2145
Website Scanner-Https WWW - Demoblaze.com-20250506-2145
https://www.demoblaze.com/
The Light Website Scanner didn't check for critical issues like SQLi, XSS, Command Injection, XXE, etc. Upgrade to run Deep scans with 40+ tests and detect more
vulnerabilities.
Summary
Findings
Risk
CVSS CVE Summary Affected software
Level
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. More details at:
https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/
4.3 CVE-2019-11358 Jquery 3.2.1
https://github.com/jquery/jquery/commit/753d591aea698e57d6db58c9f722cd0808619b1b
https://nvd.nist.gov/vuln/detail/CVE-2019-11358
passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(),
4.3 CVE-2020-11023 and others) may execute untrusted code. More details at: Jquery 3.2.1
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
Regex in its jQuery.htmlPrefilter sometimes may introduce XSS. More details at:
4.3 CVE-2020-11022 Jquery 3.2.1
https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/
Details
Risk description:
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system.
Recommendation:
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification:
CWE : CWE-1026
OWASP Top 10 - 2017 : A9 - Using Components with Known Vulnerabilities
OWASP Top 10 - 2021 : A6 - Vulnerable and Outdated Components
URL Evidence
Response headers do not include the Referrer-Policy HTTP security header as well as the <meta> tag with name 'referrer' is not present in the response.
https://www.demoblaze.com/
Request / Response
Details
Risk description:
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the
Referer header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation:
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value no-referrer of this header instructs the browser to omit the Referer header
entirely.
References:
https://developer.mozilla.org/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns
Classification:
CWE : CWE-693
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
URL Evidence
Details
Risk description:
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive
information (e.g. session cookies).
Recommendation:
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows:
The parameter max-age gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check.
1/8
The flag includeSubDomains defines that the policy applies also for sub domains of the sender of the response.
Classification:
CWE : CWE-693
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
URL Evidence
Response does not include the HTTP Content-Security-Policy security header or meta tag
https://www.demoblaze.com/
Request / Response
Details
Risk description:
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation:
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
References:
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
Classification:
CWE : CWE-693
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
URL Evidence
Details
Risk description:
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation:
We recommend setting the X-Content-Type-Options header such as X-Content-Type-Options: nosniff .
References:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
Classification:
CWE : CWE-693
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Request / Response
2/8
The following form sends inputs of type password plainly in
the URL:
<form>
<div class="form-group">
<label class="form-control-label" for="sign-username"
>
Username:
</label>
<input class="form-control" id="sign-username" type="
text"/>
</div>
<div class="form-group">
<label class="form-control-label" for="sign-password"
>
Password:
</label>
<input class="form-control" id="sign-password" type="
password"/>
</div>
<div class="form-group">
<label class="form-control-label" id="errors" style="
Headers: color:red">
https://www.demoblaze.com/cart.html GET User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) </label>
Chrome/108.0.0.0 Safari/537.36 </div>
</form>
Request / Response
Request / Response
Details
Risk description:
Passwords submitted in URLs have a higher chance of being leaked. The main reason is that URLs can be leaked in browser cross-site requests via the Referer header. Additionally, URLs are usually stored in all kinds of
logs. If any access or error logs of the server were publicly accessible, an attacker could also harvest password from it.
Recommendation:
You should submit passwords using POST rather than GET. This way sensitive data won't be shared to other locations via URLs.
References:
https://developer.mozilla.org/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns
Classification:
OWASP Top 10 - 2021 : A4 - Insecure Design
Bootstrap UI frameworks
google-frontend-httpserver Miscellaneous
Details
Risk description:
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation:
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
References:
https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/01-Information_Gathering/02-Fingerprint_Web_Server.html
Classification:
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Screenshot:
3/8
Figure 1. Website Screenshot
URL Evidence
Request / Response
Details
Risk description:
The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.
Recommendation:
Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.
References:
https://pentest-tools.com/network-vulnerability-scanning/password-auditor
http://capec.mitre.org/data/definitions/16.html
Screenshot:
URL
Missing: https://www.demoblaze.com/.well-known/security.txt
Details
Risk description:
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation:
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
4/8
References:
https://securitytxt.org/
Classification:
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Email Address:
Headers: [email protected]
https://www.demoblaze.com/ GET
User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36
Request / Response
Details
Risk description:
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation:
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a
compartment outside of the safe area.
References:
https://owasp.org/Top10/A04_2021-Insecure_Design/
Classification:
CWE : CWE-200
OWASP Top 10 - 2017 : A6: Security Misconfiguration
OWASP Top 10 - 2021 : A4: Insecure Design
Spider results
5/8
https://www.demoblaze.com/node_modules/videojs-contrib-hls/ GET 404 Not Found 310 B 404
Details
Risk description:
The table contains all the unique pages the scanner found. The duplicated URLs are not available here as scanning those is considered unnecessary
Recommendation:
We recommend to advanced users to make sure the scan properly detected most of the URLs in the application.
References:
All the URLs the scanner found, including duplicates (available for 90 days after the scan date)
Website is accessible.
Nothing was found for domain too loose set for cookies.
Nothing was found for mixed content between HTTP and HTTPS.
6/8
Nothing was found for HttpOnly flag of cookie.
Nothing was found for unsafe HTTP header Content Security Policy.
7/8
Scan parameters
target: https://www.demoblaze.com/
scan_type: Light
authentication: False
Scan stats
Unique Injection Points Detected: 3
URLs spidered: 47
Total number of HTTP requests: 15019
Average time until a response was
1ms
received:
Total number of HTTP request errors: 282
8/8