Vulnerability Scan Result

Target:

https://www.trendmicro.com/ (redirect)

Scanned target: https://www.trendmicro.com/en_gb/business.html

Submitted: Nov 01, 2025 from ID

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Trend Micro (UK) \| Global Enterprise AI Cybersecurity Platform
Description:	Enterprise AI cybersecurity platform with layered protection, cyber risk exposure management and SecOps—62 global offices, the United Kingdom office is in London.

IP Information

ip_address	23.214.208.155
country	GB
network_name	Akamai Technologies Inc
asn	AS16625

Open Ports

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

Web Technologies

Software / Version	Category
Adobe Dynamic Media Classic	Digital asset management
Google Analytics	Analytics
Google Font API	Font scripts
Java	Programming languages
jQuery	JavaScript libraries
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
Sectigo	SSL/TLS certificate authorities
Swiper	JavaScript libraries
Tealium	Tag managers, Customer data platform
Adobe Experience Manager	CMS
OneTrust	Cookie compliance
YouTube	Video players

Web Application Vulnerabilities

Evidence

URL	Method	Parameters	Evidence
https://www.trendmicro.com/en_gb/business.html	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	Suspicious comment bug found in: `<!-- FB: nested-hero-padding-bug -->`

Vulnerability description

We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.

Risk description

The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.

Recommendation

Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.

Classification

CWE	CWE-209
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://www.trendmicro.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
https://www.trendmicro.com/en_gb/business.html	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

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

Evidence

URL Evidence

URL	Evidence
https://www.trendmicro.com/en_gb/business.html	Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). default-src: https: URI in default-src allows the execution of unsafe scripts. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: http: URI in default-src allows the execution of unsafe scripts. default-src: data: URI in default-src allows the execution of unsafe scripts. object-src: We recommend restricting object-src to 'none'. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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.trendmicro.com/en_gb/business.html

Response headers include the HTTP Content-Security-Policy security header with the following security issues:frame-ancestors: This directive tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. The recommended value is 'none' or 'self'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). default-src: https: URI in default-src allows the execution of unsafe scripts. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: http: URI in default-src allows the execution of unsafe scripts. default-src: data: URI in default-src allows the execution of unsafe scripts. object-src: We recommend restricting object-src to 'none'. default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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.trendmicro.com/en_gb/business.html	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

Software / Version	Category
Adobe Dynamic Media Classic	Digital asset management
Google Analytics	Analytics
Google Font API	Font scripts
Java	Programming languages
jQuery	JavaScript libraries
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
Sectigo	SSL/TLS certificate authorities
Swiper	JavaScript libraries
Tealium	Tag managers, Customer data platform
Adobe Experience Manager	CMS
OneTrust	Cookie compliance
YouTube	Video players

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.

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Adobe Experience Manager	CMS
Java	Programming languages
Nginx	Web servers, Reverse proxies
YouTube	Video players
Tealium	Tag managers, Customer data platform
Sectigo	SSL/TLS certificate authorities
OneTrust	Cookie compliance
jQuery	JavaScript libraries
Google Font API	Font scripts
Open Graph	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.

Evidence

Domain Queried	DNS Record Type	Description	Value
www.trendmicro.com	A	IPv4 address	23.214.208.155
www.trendmicro.com	CNAME	Canonical name	ion.trendmicro.com.edgekey.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.