Vulnerability Scan Result

Target:

https://www.sheria.go.tz/

Scanned target: https://www.sheria.go.tz/

Submitted: Jun 12, 2026 from MX

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	MoCLA \| Wizara ya Katiba na Sheria - Mwanzo
Description:	Tume ya Taifa ya Uchaguzi (NEC) ni Taasisi huru ya Serikali iliyoanzishwa mwaka 1993 chini ya Ibara ya 74(1) ya Katiba ya Jamhuri ya Muungano wa Tanzania ya Mwaka 1977 \| Wizara ya Katiba na Sheria - Mwanzo

IP Information

ip_address	197.149.178.6
country	TZ
network_name	Tanzania e-Government Agency
asn	AS327795

Open Ports

80/tcp	http	Apache httpd -
443/tcp	https	Apache httpd -
2083/tcp	radsec	- -
2086/tcp	gnunet	- -
2087/tcp	eli	- -

Web Technologies

Software / Version	Category
ClientJS	JavaScript libraries, Browser fingerprinting
DataTables 1.13.1	JavaScript libraries
Magnific Popup	JavaScript libraries
Bootstrap 4.6.2	UI frameworks
particles.js	JavaScript graphics
Apache HTTP Server	Web servers
jQuery 3.6.3	JavaScript libraries
Slick	JavaScript libraries
Google Maps	Maps
OWL Carousel	JavaScript libraries
Swiper	JavaScript libraries
DigiCert	SSL/TLS certificate authorities
HSTS	Security
Cart Functionality	Ecommerce

Web Application Vulnerabilities

Evidence

URL	Evidence
https://www.sheria.go.tz/	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.

Vulnerability description

We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.

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.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.sheria.go.tz/	Response does not include the HTTP Content-Security-Policy security header or meta tag

Vulnerability description

We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.

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.

Classification

CWE	CWE-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
ClientJS	JavaScript libraries, Browser fingerprinting
DataTables 1.13.1	JavaScript libraries
Magnific Popup	JavaScript libraries
Bootstrap 4.6.2	UI frameworks
particles.js	JavaScript graphics
Apache HTTP Server	Web servers
jQuery 3.6.3	JavaScript libraries
Slick	JavaScript libraries
Google Maps	Maps
OWL Carousel	JavaScript libraries
Swiper	JavaScript libraries
DigiCert	SSL/TLS certificate authorities
HSTS	Security
Cart Functionality	Ecommerce

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

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.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Parameters	Evidence
https://www.sheria.go.tz/	GET	Headers: 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	Email Address: km@sheria.go.tz

Vulnerability description

We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.

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.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Method	Summary
https://www.sheria.go.tz/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

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.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://www.sheria.go.tz/.well-known/security.txt

Vulnerability description

We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.

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.

Classification

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Apache HTTP Server	Web servers
DigiCert	SSL/TLS certificate authorities

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

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.

Evidence

Software / Version	Category
Apache HTTP Server	Web servers

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

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.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.sheria.go.tz	A	IPv4 address	197.149.178.6
www.sheria.go.tz	NS	Name server	ns1.eganet.go.tz
www.sheria.go.tz	NS	Name server	ns2.eganet.go.tz
www.sheria.go.tz	NS	Name server	ns3.eganet.go.tz
www.sheria.go.tz	MX	Mail server	10 mx6.eganet.go.tz
www.sheria.go.tz	SOA	Start of Authority	ns.eganet.go.tz. hostmaster.sheria.go.tz. 2018020145 3600 1800 1209600 3600
www.sheria.go.tz	TXT	Text record	"_hoykt5aqgohg0txgqlufkvmiqu00sxj"
www.sheria.go.tz	SPF	Sender Policy Framework	"v=spf1 a:smtp2.eganet.go.tz a:smtp3.eganet.go.tz a:smtp.eganet.go.tz a:smtp.gov.go.tz a:smtp4.eganet.go.tz a:smtp6.eganet.go.tz ~all"
www.sheria.go.tz	CNAME	Canonical name	sheria.go.tz

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.