Vulnerability Scan Result

Target:

http://heathrow.com/ (redirect)

Scanned target: https://www.heathrow.com/

Submitted: Mar 23, 2026 from CI

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Heathrow: Welcome to Heathrow Airport \| Heathrow
Description:	Heathrow is the UK’s biggest airport, located 14 miles west of Central London and serving hundreds of destinations around the world.

IP Information

ip_address	13.107.246.60
country	US
network_name	Microsoft Corporation
asn	AS8075

ip_address	13.107.213.60
country	US
network_name	Microsoft Corporation
asn	AS8075

Open Ports

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

Web Technologies

Software / Version	Category
AppNexus	Advertising
Amazon Web Services	PaaS
Amazon CloudFront	CDN
Amazon ALB	Load balancers
Azure	PaaS
Adobe Experience Platform Identity Service	Customer data platform
Adobe Experience Platform Launch	Tag managers
Azure Front Door	Load balancers
Tealium Consent Management	Cookie compliance
LazySizes	JavaScript libraries, Performance
core-js 3.46.0	JavaScript libraries
Java	Programming languages
Open Graph	Miscellaneous
PWA	Miscellaneous
Webpack	Miscellaneous
AddToAny	Widgets
Adobe Analytics	Analytics
Adobe Experience Manager	CMS
DigiCert	SSL/TLS certificate authorities
reCAPTCHA	Security
Lodash 4.17.15	JavaScript libraries
HSTS	Security
Salesforce Interaction Studio	Personalisation, Segmentation
ServiceNow	Miscellaneous

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2020-8203	7.4	0.02826	0.86028	Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
CVE-2021-23337	7.2	0.00517	0.66478	Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
CVE-2025-13465	6.9	0.00028	0.07846	Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23
CVE-2020-28500	5.3	0.00245	0.47541	Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

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. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

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-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://www.heathrow.com/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

URL Evidence

URL	Evidence
https://www.heathrow.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`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'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.`

https://www.heathrow.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues: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'. script-src: script-src directive is missing. object-src: Missing object-src allows the injection of plugins which can execute JavaScript. We recommend setting it to 'none'. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified.

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-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
AppNexus	Advertising
Amazon Web Services	PaaS
Amazon CloudFront	CDN
Amazon ALB	Load balancers
Azure	PaaS
Adobe Experience Platform Identity Service	Customer data platform
Adobe Experience Platform Launch	Tag managers
Azure Front Door	Load balancers
Tealium Consent Management	Cookie compliance
LazySizes	JavaScript libraries, Performance
core-js 3.46.0	JavaScript libraries
Java	Programming languages
Open Graph	Miscellaneous
PWA	Miscellaneous
Webpack	Miscellaneous
AddToAny	Widgets
Adobe Analytics	Analytics
Adobe Experience Manager	CMS
DigiCert	SSL/TLS certificate authorities
reCAPTCHA	Security
Lodash 4.17.15	JavaScript libraries
HSTS	Security
Salesforce Interaction Studio	Personalisation, Segmentation
ServiceNow	Miscellaneous

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
Missing: https://www.heathrow.com/.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

Evidence

URL	Method	Parameters	Evidence
https://www.heathrow.com/	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: `/root/responsivegrid/terminaltransferdeta` `/bin/heathrow/featureFlag` `/bin/heathrow/partnerCSS.en.json` `/root/responsivegrid/relatedcarousel` `/root/responsivegrid/stepbystep` `/bin/heathrow/terminalLanding.en.json` `/bin/heathrow/airportListing.en.json` `/bin/heathrow/destinationDetail.en.json` `/bin/heathrow/ttg/questionnaire.en.json` `/bin/heathrow/accordionSearch` `/root/responsivegrid/loungecards` `/bin/heathrow/destinationSearch.en.json` `/bin/heathrow/ttg/questionnaire/all.en.json` `/root/responsivegrid/adventoffer` `/root/responsivegrid/traveltips` `/bin/heathrow/advisoryNotification.en.json` `/bin/heathrow/ttg/content.en.json`

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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Adobe Experience Manager	CMS
Java	Programming languages
Amazon ALB	Load balancers
Azure Front Door	Load balancers
Azure	PaaS
Amazon Web Services	PaaS
Salesforce Interaction Studio	Personalisation, Segmentation
reCAPTCHA	Security
AddToAny	Widgets
HSTS	Security
DigiCert	SSL/TLS certificate authorities
Amazon CloudFront	CDN

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.heathrow.com	A	IPv4 address	13.107.246.60
www.heathrow.com	A	IPv4 address	13.107.213.60
www.heathrow.com	AAAA	IPv6 address	2620:1ec:bdf::60
www.heathrow.com	AAAA	IPv6 address	2620:1ec:46::60
www.heathrow.com	CNAME	Canonical name	halcs-it-cto-gk-frontdoor-prod.azurefd.net

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.

Operating System	Accuracy
FreeBSD 11.0-STABLE	91%

Evidence

Software / Version	Category
Adobe Experience Manager	CMS
Java	Programming languages
Azure Front Door	Load balancers
Amazon ALB	Load balancers
Azure	PaaS
Amazon Web Services	PaaS
HSTS	Security
DigiCert	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Salesforce Interaction Studio	Personalisation, Segmentation
reCAPTCHA	Security
AddToAny	Widgets

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.