Vulnerability Scan Result

Target:

https://mobile-deeplink.clearme.com/s/c/TBhf6iPfCxD9Skby7zzKoolBee7Z3oaHyMosWnBKdWqNV2V2xE8Sw2ezxB20Tvs0dOpZS7SfVfiYghnz4tQEFt7gw8EjPdUOyOKIljjaAF2MiBHQnplmd11GnmEWooL1W8ymj6l2cPGXzlKx-Drfa4lsfqZgJM16d8EdCm-4Dw3EpRRwYOUmbNxuEGIGC3SaPULFfFQvHnXyHJOfK1GRvJnqVuv_RiN2Yc0FTsYPJ6TwDan479cApJI9KAr4T0Cxn8CQ1yLmMnXOnUd_zFfOdWl9Wn5BlTXP5ruvYOWpgu9SQpsGvhX2Q1kd85Ck8T_FmyEvy6-n-gY8SovuKWqdbOtB5JUqp6o7n6PEquD85tfgJsowACYQ1FSgE5851S7b/WMVE3POKYGuKVBBH9Kl9Ng9oIrurIi22/8 (redirect)

Scanned target: https://www.clearme.com/support?utm_source=Iterable&utm_medium=email&utm_campaign=campaign_13264229

Submitted: April 18, 2025 from FR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

https://mobile-deeplink.clearme.com/s/c/TBhf6iPfCxD9Skby7zzKoolBee7Z3oaHyMosWnBKdWqNV2V2xE8Sw2ezxB20Tvs0dOpZS7SfVfiYghnz4tQEFt7gw8EjPdUOyOKIljjaAF2MiBHQnplmd11GnmEWooL1W8ymj6l2cPGXzlKx-Drfa4lsfqZgJM16d8EdCm-4Dw3EpRRwYOUmbNxuEGIGC3SaPULFfFQvHnXyHJOfK1GRvJnqVuv_RiN2Yc0FTsYPJ6TwDan479cApJI9KAr4T0Cxn8CQ1yLmMnXOnUd_zFfOdWl9Wn5BlTXP5ruvYOWpgu9SQpsGvhX2Q1kd85Ck8T_FmyEvy6-n-gY8SovuKWqdbOtB5JUqp6o7n6PEquD85tfgJsowACYQ1FSgE5851S7b/WMVE3POKYGuKVBBH9Kl9Ng9oIrurIi22/8

Title:	Support & Frequently Asked Questions (FAQs) \| CLEAR
Description:	Get help with your CLEAR Plus Membership, account, and services. Visit CLEAR Support for answers to FAQs or assistance with your membership.

IP Information

IP address	18.144.119.190
Country	US
AS number	AS16509
Net name	Amazon Inc

Open Ports

80/tcp	http	OpenResty web app server -
443/tcp	https	openresty -

Web Technologies

Software / Version	Category
Cloudflare	CDN
DigiCert	SSL/TLS certificate authorities
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Evidence
https://www.clearme.com/support	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	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL	Evidence
https://www.clearme.com/support	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-693
OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

Software / Version	Category
Cloudflare	CDN
DigiCert	SSL/TLS certificate authorities
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.

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Evidence

URL
https://www.clearme.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).

Classification

OWASP Top 10 - 2017	A6 - Security Misconfiguration
OWASP Top 10 - 2021	A5 - Security Misconfiguration

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
mobile-deeplink.clearme.com	A	IPv4 address	18.144.119.190
mobile-deeplink.clearme.com	SPF	Sender Policy Framework	"v=spf1 -all"
mobile-deeplink.clearme.com	CAA	Certificate Authority Authorization	0 issue "digicert.com"
mobile-deeplink.clearme.com	CAA	Certificate Authority Authorization	0 issue "entrust.net"
mobile-deeplink.clearme.com	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
mobile-deeplink.clearme.com	CNAME	Canonical name	thirdparty.bnc.lt

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.

Evidence

Software / Version	Category
Nginx	Web servers, Reverse proxies
OpenResty	Web servers
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.