Vulnerability Scan Result

Target:

https://app.myprivacyassist.com/single-alert/019cff96-42d2-40d7-a37b-39af156c782a

Scanned target: https://app.myprivacyassist.com/single-alert/019cff96-42d2-40d7-a37b-39af156c782a

Submitted: Mar 22, 2026 from KR

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	No title found
Description:	No description found

IP Information

ip_address	18.173.205.9
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	18.173.205.66
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	18.173.205.26
country	US
network_name	Amazon.com, Inc.
asn	AS16509

ip_address	18.173.205.95
country	US
network_name	Amazon.com, Inc.
asn	AS16509

Open Ports

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

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Amazon S3	CDN
Adobe Fonts	Font scripts
Google Font API	Font scripts
Plaid	Payment processors, Miscellaneous
Recurly	Payment processors
Typekit	Font scripts
PWA	Miscellaneous
Google Tag Manager	Tag managers
HSTS	Security
Zuora	Payment processors

Web Application Vulnerabilities

Evidence

URL
https://app.myprivacyassist.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

Software / Version	Category
Amazon Web Services	PaaS
AWS Certificate Manager	SSL/TLS certificate authorities
Amazon CloudFront	CDN
Amazon S3	CDN
Adobe Fonts	Font scripts
Google Font API	Font scripts
Plaid	Payment processors, Miscellaneous
Recurly	Payment processors
Typekit	Font scripts
PWA	Miscellaneous
Google Tag Manager	Tag managers
HSTS	Security
Zuora	Payment processors

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 Evidence

URL	Evidence
https://app.myprivacyassist.com/single-alert/019cff96-42d2-40d7-a37b-39af156c782a	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'. object-src: We recommend restricting object-src to 'none'. 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'. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

https://app.myprivacyassist.com/single-alert/019cff96-42d2-40d7-a37b-39af156c782a

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'. object-src: We recommend restricting object-src to 'none'. 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'. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. default-src: data: URI in default-src allows the execution of unsafe scripts. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Zuora	Payment processors
Recurly	Payment processors
HSTS	Security
Amazon S3	CDN
Amazon CloudFront	CDN
AWS Certificate Manager	SSL/TLS certificate authorities
Typekit	Font scripts
Google Tag Manager	Tag managers
Adobe Fonts	Font scripts
Plaid	Payment processors, 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
app.myprivacyassist.com	A	IPv4 address	18.173.205.9
app.myprivacyassist.com	A	IPv4 address	18.173.205.95
app.myprivacyassist.com	A	IPv4 address	18.173.205.26
app.myprivacyassist.com	A	IPv4 address	18.173.205.66

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.