Vulnerability Scan Result
IP address | 76.76.21.142 |
Country | US |
AS number | AS16509 |
Net name | Amazon Inc |
80/tcp | http | Vercel |
443/tcp | https | Vercel |
Software / Version | Category |
---|---|
dc.js | JavaScript graphics, JavaScript libraries |
Emotion | JavaScript frameworks, Development |
core-js 3.39.0 | JavaScript libraries |
Google Font API | Font scripts |
Highlight.js | JavaScript libraries |
MUI | UI frameworks |
NextAuth.js | Authentication |
Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
Node.js | Programming languages |
Open Graph | Miscellaneous |
React | JavaScript frameworks |
Segment | Customer data platform |
Sentry | Issue trackers |
Vercel | PaaS |
PWA | Miscellaneous |
Webpack | Miscellaneous |
Module Federation | Miscellaneous |
DigitalOcean Spaces | CDN, IaaS |
Hotjar | Analytics |
Lodash 4.17.21 | JavaScript libraries |
HSTS | Security |
Web Application Vulnerabilities
Evidence
URL | Evidence |
---|---|
https://house-m.weticket.io/house-m | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the <code>X-Content-Type-Options</code> header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
CWE | CWE-693 |
OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
URL | Evidence |
---|---|
https://house-m.weticket.io/house-m | 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.
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
URL | Evidence |
---|---|
https://house-m.weticket.io/house-m | 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 <code>Referrer-Policy</code> HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
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
Software / Version | Category |
---|---|
dc.js | JavaScript graphics, JavaScript libraries |
Emotion | JavaScript frameworks, Development |
core-js 3.39.0 | JavaScript libraries |
Google Font API | Font scripts |
Highlight.js | JavaScript libraries |
MUI | UI frameworks |
NextAuth.js | Authentication |
Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
Node.js | Programming languages |
Open Graph | Miscellaneous |
React | JavaScript frameworks |
Segment | Customer data platform |
Sentry | Issue trackers |
Vercel | PaaS |
PWA | Miscellaneous |
Webpack | Miscellaneous |
Module Federation | Miscellaneous |
DigitalOcean Spaces | CDN, IaaS |
Hotjar | Analytics |
Lodash 4.17.21 | JavaScript libraries |
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.
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
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.
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 |
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
Domain Queried | DNS Record Type | Description | Value |
---|---|---|---|
house-m.weticket.io | A | IPv4 address | 66.33.60.130 |
house-m.weticket.io | A | IPv4 address | 76.76.21.164 |
house-m.weticket.io | CAA | Certificate Authority Authorization | 0 issue "letsencrypt.org" |
house-m.weticket.io | CAA | Certificate Authority Authorization | 0 issue "globalsign.com" |
house-m.weticket.io | CAA | Certificate Authority Authorization | 0 issue "sectigo.com" |
house-m.weticket.io | CNAME | Canonical name | cname.vercel-dns.com |
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.
Vulnerability description
OS detection couldn't determine the operating system.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.