Website Vulnerability Scanner Report

 https://dukaanye.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

Overall risk level: Risk ratings: Scan information:

Medium High: 0 Start time: Feb 26, 2024 / 11:36:15
Medium: 1 Finish time: Feb 26, 2024 / 11:37:47

Low: 5 Scan duration: 1 min, 32 sec

Info: 12 Tests performed: 18/18

Scan status: Finished

Findings

 Insecure cookie setting: missing HttpOnly flag CONFIRMED

Cookie
URL Evidence
Name

The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag:
Set-Cookie: XSRF-
TOKEN=eyJpdiI6IldJT0RGbWwxejluSlI3R2FReW5KVEE9PSIsInZhbHVlIjoib2hzck52blZSNkd1L21wRV
XSRF-
https://dukaanye.com/ FGeGJEWmRTMXdWYm1qT0svTmFQYmtLcU1xUEc4VVF3UVdSU3RnV29XK3NvcGwydW5NWFBvV
TOKEN
mM5ekxMb3dSU1lnbG52enVkSit5WDRxUTNMSUhpSGpQN0c4VFNuN29qQ0JPRmRKbEJSZTg1blUr
UngiLCJtYWMiOiIyMWQ4ODQ3ZDUzYmU3ZWM3ZWY3OGI5MGE0OWVjOGNhYjkwYTE3OGJhMGQz
ZGY4ZjJhZjllYTE5M2Q5ZTAxYjg4IiwidGFnIjoiIn0%3D

 Details

Risk description:
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie
and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation:
Ensure that the HttpOnly flag is set for all cookies.

References:
https://owasp.org/www-community/HttpOnly

Classification:
CWE : CWE-1004
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

 Missing security header: Strict-Transport-Security CONFIRMED

URL Evidence

https://dukaanye.com/ Response headers do not include the HTTP Strict-Transport-Security header

 Details

1/5
 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:

Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]

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.
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 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

 Missing security header: Referrer-Policy CONFIRMED

URL Evidence

Response headers do not include the Referrer-Policy HTTP security header as well as the <meta> tag with
https://dukaanye.com/
name 'referrer' is not present in the 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 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

 Missing security header: Content-Security-Policy CONFIRMED

URL Evidence

https://dukaanye.com/ Response does not include the HTTP Content-Security-Policy security header or meta tag

 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 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

2/5
 Missing security header: X-Content-Type-Options CONFIRMED

URL Evidence

https://dukaanye.com/ Response headers do not include the X-Content-Type-Options HTTP security header

 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 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

 Server software and technology found UNCONFIRMED 

Software / Version Category

Cloudflare CDN

HTTP/3 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 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

 Security.txt file is missing CONFIRMED

URL

Missing: https://dukaanye.com/.well-known/security.txt

 Details

Risk description:
We have detected that the server is missing the security.txt file. There is no particular risk in not creating a valid 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.

References:
https://securitytxt.org/

3/5
 Classification:
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration

 Website is accessible.

 Nothing was found for vulnerabilities of server-side software.

 Nothing was found for client access policies.

 Nothing was found for robots.txt file.

 Nothing was found for use of untrusted certificates.

 Nothing was found for enabled HTTP debug methods.

 Nothing was found for secure communication.

 Nothing was found for directory listing.

 Nothing was found for domain too loose set for cookies.

 Nothing was found for Secure flag of cookie.

 Nothing was found for unsafe HTTP header Content Security Policy.

Scan coverage information

List of tests performed (18/18)

 Checking for website accessibility...
 Checking for missing HTTP header - Strict-Transport-Security...
 Checking for missing HTTP header - Referrer...
 Checking for missing HTTP header - Content Security Policy...
 Checking for missing HTTP header - X-Content-Type-Options...
 Checking for HttpOnly flag of cookie...
 Checking for website technologies...
 Checking for vulnerabilities of server-side software...
 Checking for client access policies...
 Checking for robots.txt file...
 Checking for absence of the security.txt file...
 Checking for use of untrusted certificates...
 Checking for enabled HTTP debug methods...
 Checking for secure communication...
 Checking for directory listing...
 Checking for domain too loose set for cookies...
 Checking for Secure flag of cookie...
 Checking for unsafe HTTP header Content Security Policy...

4/5
Scan parameters
Target: https://dukaanye.com/
Scan type: Light
Authentication: False

Scan stats
Unique Injection Points Detected: 313
URLs spidered: 2
Total number of HTTP requests: 10
Average time until a response was
1442ms
received:

5/5