Website Vulnerability Scanner Report (Light)

Unlock the full capabilities of this scanner

See what the DEEP scanner can do

Perform in-depth website scanning and discover high risk vulnerabilities.

Testing areas Light scan Deep scan

Website fingerprinting  
Version-based vulnerability detection  

Common configuration issues  

SQL injection  
Cross-Site Scripting  

Local/Remote File Inclusion  

Remote command execution  

Discovery of sensitive files  

 https://www.nssf.go.tz/
Target added due to a redirect from https://www.nssf.go.tz

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: Aug 24, 2024 / 11:43:23 UTC+03
Medium: 2 Finish time: Aug 24, 2024 / 11:43:53 UTC+03
Low: 6 Scan duration: 30 sec

Info: 11 Tests performed: 19/19

Scan status: Finished

Findings

 Insecure cookie setting: missing HttpOnly flag CONFIRMED

Cookie
URL Evidence
Name

1/6
 The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag:
Set-Cookie: XSRF-
TOKEN=eyJpdiI6IkJYZGFTVjlYUEFPbEpJMEJIOU85XC93PT0iLCJ2YWx1ZSI6IkxJR3NBZEtWMUZ1eHFSW
XSRF- ktNbW50RTdadk15RW94MlZlSUVzTHBsQW9NditTKzNwUHh2TFNnekVBOTR4Z0t2NmYiLCJtYWMiOiJjM
https://www.nssf.go.tz/ WJlNTI2ZDZmYTYxYzM5OGVkYWJhNmZiYzk1ODExOTFkZDY3OTE4Y2IzNWM1MDdjZjg0ZmIxZjc0NzdjN
TOKEN
GMwIn0%3D

Request / Response

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

 Insecure cookie setting: missing Secure flag CONFIRMED

Cookie
URL Evidence
Name

Set-Cookie: XSRF-
TOKEN=eyJpdiI6IkJYZGFTVjlYUEFPbEpJMEJIOU85XC93PT0iLCJ2YWx1ZSI6IkxJR3NBZEtWMUZ1eHFSW
ktNbW50RTdadk15RW94MlZlSUVzTHBsQW9NditTKzNwUHh2TFNnekVBOTR4Z0t2NmYiLCJtYWMiOiJjM
WJlNTI2ZDZmYTYxYzM5OGVkYWJhNmZiYzk1ODExOTFkZDY3OTE4Y2IzNWM1MDdjZjg0ZmIxZjc0NzdjN
GMwIn0%3D; expires=Sat, 24-Aug-2024 08:47:49 GMT; Max-Age=300; path=/,
XSRF-
https://www.nssf.go.tz/ nssf_session=eyJpdiI6ImVWT2NiR2ZYcUFmV2RUMmZacnRsaWc9PSIsInZhbHVlIjoiemp3RzhkTEI3elNEaX
TOKEN
BacTVKaEdxa09PbnVzWFR5QTBpUytBdnF0WW9lR2doTUJIZGRmeHhPUGtSZFdBNUN6WSIsIm1hYyI6IjE4
ZTZjNGFiY2RkN2I3ZGMwM2I0ZGQyZWE4MjE2NWYxOTZiNTk3MWM1NWZhNzg2YWM1ZTUyZjE5ODQ0M
GY0N2EifQ%3D%3D; expires=Sat, 24-Aug-2024 08:47:49 GMT; Max-Age=300; path=/; httponly

Request / Response

 Details

Risk description:
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie
of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.

Recommendation:
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.

References:
https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/06-
Session_Management_Testing/02-Testing_for_Cookies_Attributes.html

Classification:
CWE : CWE-614
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration

 Missing security header: Strict-Transport-Security CONFIRMED

URL Evidence

https://www.nssf.go.tz/ Response headers do not include the HTTP Strict-Transport-Security header

Request / Response

2/6
  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:

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 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - 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 name
https://www.nssf.go.tz/ 'referrer' is not present in the response.
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

 Missing security header: Content-Security-Policy CONFIRMED

URL Evidence

Response does not include the HTTP Content-Security-Policy security header or meta tag
https://www.nssf.go.tz/
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

3/6
 Missing security header: X-Content-Type-Options CONFIRMED

URL Evidence

Response headers do not include the X-Content-Type-Options HTTP security header

https://www.nssf.go.tz/
Request / Response

 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

 Robots.txt file found CONFIRMED

URL

https://www.nssf.go.tz/robots.txt

 Details

Risk description:
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be
considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation:
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website
(ex. administration panels, configuration files, etc).

References:
https://www.theregister.co.uk/2015/05/19/robotstxt/

Classification:
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration

 Server software and technology found UNCONFIRMED 

Software / Version Category

ClientJS JavaScript libraries, Browser fingerprinting

Bootstrap 4.3.1 UI frameworks

Apache HTTP Server Web servers

jQuery 3.7.0 JavaScript libraries

Slick JavaScript libraries

DigiCert SSL/TLS certificate authorities

 Details

Risk description:
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

4/6
 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

 Security.txt file is missing CONFIRMED

URL

Missing: https://www.nssf.go.tz/.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.

References:
https://securitytxt.org/

Classification:
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration

 HTTP OPTIONS enabled CONFIRMED

URL Method Summary

We did a HTTP OPTIONS request.

https://www.nssf.go.tz/ OPTIONS
The server responded with a 200 status code and the header: Allow: GET,HEAD
Request / Response

 Details

Risk description:
The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if
any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation:
We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your
webserver configuration.

References:
https://techcommunity.microsoft.com/t5/iis-support-blog/http-options-and-default-page-vulnerabilities/ba-p/1504845
https://docs.nginx.com/nginx-management-suite/acm/how-to/policies/allowed-http-methods/

Classification:
CWE : CWE-16
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration

 Website is accessible.

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

5/6
 Nothing was found for client access policies.

 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 unsafe HTTP header Content Security Policy.

Scan coverage information

List of tests performed (19/19)

 Starting the scan...
 Checking for missing HTTP header - Strict-Transport-Security...
 Checking for missing HTTP header - Referrer...
 Checking for missing HTTP header - Content Security Policy...
 Checking for HttpOnly flag of cookie...
 Checking for missing HTTP header - X-Content-Type-Options...
 Checking for Secure 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 enabled HTTP OPTIONS method...
 Checking for secure communication...
 Checking for directory listing...
 Checking for domain too loose set for cookies...
 Checking for unsafe HTTP header Content Security Policy...

Scan parameters
Target: https://www.nssf.go.tz/
Scan type: Light
Authentication: False

Scan stats
Unique Injection Points Detected: 72
URLs spidered: 15
Total number of HTTP requests: 24
Average time until a response was
391ms
received:

6/6