Vulnerability Scan Result

Target:

https://click.info.national-lottery.co.uk/?qs=5f7d48dac2d4553c6b2124d8cc535c8322e693e9993d8b5ab9dd1e82ee503a44980da184dfeff95192b59928ba0d423d77f77b1b33af87d7a9c152f62e42ca3d (redirect)

Scanned target: https://www.national-lottery.co.uk/login/auth

Submitted: Nov 04, 2025 from AL

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Sign in \| The National Lottery
Description:	Sign in to your National Lottery account

IP Information

ip_address	194.246.78.103
country	GB
network_name	British Telecommunications PLC
asn	AS2856

Open Ports

80/tcp	http	- -
443/tcp	https	Camelot -

Web Technologies

Software / Version	Category
Google Ads	Advertising
Tealium Consent Management	Cookie compliance
jQuery 3.7.1	JavaScript libraries
Knockout.js 3.5.1	JavaScript frameworks
LottieFiles 5.11.0	Miscellaneous
Moment.js 2.29.4	JavaScript libraries
Open Graph	Miscellaneous
Google Ads Conversion Tracking	Analytics
Tealium	Tag managers, Customer data platform
DigiCert	SSL/TLS certificate authorities
Lodash 1.13.6	JavaScript libraries
HSTS	Security
JSP	Web frameworks

Web Application Vulnerabilities

Evidence

URL Evidence

URL	Evidence
https://www.national-lottery.co.uk/login/auth	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'.`

https://www.national-lottery.co.uk/login/auth

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none'. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

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

Evidence

URL	Evidence
https://www.national-lottery.co.uk/login/auth	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
https://www.national-lottery.co.uk/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

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).

Evidence

Software / Version	Category
Google Ads	Advertising
Tealium Consent Management	Cookie compliance
jQuery 3.7.1	JavaScript libraries
Knockout.js 3.5.1	JavaScript frameworks
LottieFiles 5.11.0	Miscellaneous
Moment.js 2.29.4	JavaScript libraries
Open Graph	Miscellaneous
Google Ads Conversion Tracking	Analytics
Tealium	Tag managers, Customer data platform
DigiCert	SSL/TLS certificate authorities
Lodash 1.13.6	JavaScript libraries
HSTS	Security
JSP	Web frameworks

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

URL	Method	Parameters	Evidence
https://www.national-lottery.co.uk/login/auth	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	Operating system paths found in the HTTP response: `/css/app/iwg-gradient-app.css~571f`

Vulnerability description

We found operating system paths returned in a HTTP response.

Risk description

The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.

Recommendation

Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.

Classification

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

Evidence

URL	Method	Parameters	Evidence
https://www.national-lottery.co.uk/login/auth	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: help@national-lottery.co.uk

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 Evidence

URL	Evidence
https://www.national-lottery.co.uk/login/auth	`<input type="email" name="username" class="text" id="form_username" tabindex="0" autocomplete="off" aria-required="true" maxlength="50"> <input type="password" name="password" class="text showhide_on" id="form_password" tabindex="0" autocomplete="off" aria-required="true" maxlength="30"> <input type="submit" id="login_submit_bttn" name="loginSubmit" class="btn btn_primary float_right" data-badge="bottomright" value="Sign in">`

https://www.national-lottery.co.uk/login/auth

<input type="email" name="username" class="text" id="form_username" tabindex="0" autocomplete="off" aria-required="true" maxlength="50"> <input type="password" name="password" class="text showhide_on" id="form_password" tabindex="0" autocomplete="off" aria-required="true" maxlength="30"> <input type="submit" id="login_submit_bttn" name="loginSubmit" class="btn btn_primary float_right" data-badge="bottomright" value="Sign in">

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.national-lottery.co.uk	A	IPv4 address	194.246.78.103
www.national-lottery.co.uk	CNAME	Canonical name	www.lb.national-lottery.co.uk

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.