Vulnerability Scan Result

Target:

http://www.hightail.com/ (redirect)

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

Submitted: Nov 18, 2025 from YE

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Secure file sharing & creative collaboration \| Hightail by OpenText
Description:	Simple and secure file sharing with Hightail by OpenText. Keep creative projects moving in one easy and secure cloud-based software.

IP Information

ip_address	3.171.214.37
country	US
network_name	-
asn	-

ip_address	3.171.214.19
country	US
network_name	-
asn	-

ip_address	3.171.214.79
country	US
network_name	-
asn	-

ip_address	3.171.214.121
country	US
network_name	-
asn	-

Open Ports

80/tcp	http	Amazon CloudFront httpd -
443/tcp	https	CloudFront -

Web Technologies

Software / Version	Category
Microsoft Advertising	Advertising
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Amazon ELB	Load balancers
Linkedin Ads	Advertising
Linkedin Insight Tag	Analytics
Trustpilot	Reviews
cdnjs	CDN
CreateJS	CDN
D3	JavaScript graphics
dc.js	JavaScript graphics, JavaScript libraries
Express	Web frameworks, Web servers
Bootstrap f9330852	UI frameworks
Google Analytics	Analytics
Node.js	Programming languages
Open Graph	Miscellaneous
PWA	Miscellaneous
Cloudflare	CDN
Google Tag Manager	Tag managers
Hotjar	Analytics
HubSpot	Marketing automation
HubSpot Analytics	Analytics
Lodash	JavaScript libraries
Pendo	Analytics, User onboarding
HSTS	Security

Web Application Vulnerabilities

Evidence

URL
https://www.hightail.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.hightail.com/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: We recommend restricting object-src to 'none' only. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: data: URI in script-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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: Allow only resources downloaded over HTTPS.

https://www.hightail.com/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. object-src: We recommend restricting object-src to 'none' only. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: data: URI in script-src allows the execution of unsafe scripts. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. 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: Allow only resources downloaded over HTTPS.

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

Software / Version	Category
Microsoft Advertising	Advertising
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Amazon ELB	Load balancers
Linkedin Ads	Advertising
Linkedin Insight Tag	Analytics
Trustpilot	Reviews
cdnjs	CDN
CreateJS	CDN
D3	JavaScript graphics
dc.js	JavaScript graphics, JavaScript libraries
Express	Web frameworks, Web servers
Bootstrap f9330852	UI frameworks
Google Analytics	Analytics
Node.js	Programming languages
Open Graph	Miscellaneous
PWA	Miscellaneous
Cloudflare	CDN
Google Tag Manager	Tag managers
Hotjar	Analytics
HubSpot	Marketing automation
HubSpot Analytics	Analytics
Lodash	JavaScript libraries
Pendo	Analytics, User onboarding
HSTS	Security

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.hightail.com/assets/images/favicon/browserconfig.xml	GET	Query: v=2 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 Cookies: AWSALBTG=VE5pkJooEyhxpX2ZL4QRbFAdrGI6ikMxyuM9+F6dfZRPseXOwU4uS/tbRAskRKn2URFB2WiC3teJj+2mVdw1OM39AyLQ5hmXNIBYrHB9zFZ2IOuUJYX...	Possible API endpoint found at `/assets/images/favicon/browserconfig.xml`

Vulnerability description

We found API endpoints while crawling the given web application.

Risk description

These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.

Recommendation

Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.

Evidence

URL	Method	Parameters	Evidence
https://www.hightail.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: `/assets/animations/home/a1/index.html` `/assets/animations/home/a3/index.html` `/assets/animations/home/a4/index.html` `/assets/animations/home/a2/index.html`

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
Node.js	Programming languages
D3	JavaScript graphics
Bootstrap f9330852	UI frameworks
Amazon ELB	Load balancers
Amazon Web Services	PaaS
Express	Web frameworks, Web servers
Pendo	Analytics, User onboarding
Cloudflare	CDN
Trustpilot	Reviews
OneTrust	Cookie compliance
Microsoft Advertising	Advertising
Lodash	JavaScript libraries
Google Tag Manager	Tag managers
Google Analytics	Analytics
cdnjs	CDN
Linkedin Ads	Advertising
HSTS	Security
Amazon CloudFront	CDN
AWS Certificate Manager	SSL/TLS certificate authorities
Linkedin Insight Tag	Analytics
HubSpot Analytics	Analytics
HubSpot	Marketing automation
Hotjar	Analytics
dc.js	JavaScript graphics, JavaScript libraries
CreateJS	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.hightail.com	A	IPv4 address	3.171.214.121
www.hightail.com	A	IPv4 address	3.171.214.79
www.hightail.com	A	IPv4 address	3.171.214.19
www.hightail.com	A	IPv4 address	3.171.214.37

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.