Vulnerability Scan Result
| Title: | Eventbrite — entdecken Sie die besten lokalen Veranstaltungen und Aktivitäten |
| Description: | Eventbrite - Discover the Best Local Events & Things to Do |
| ip_address | 13.226.144.120 |
| country | US  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 13.226.144.6 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 13.226.144.42 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 13.226.144.5 |
| country | US |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| TikTok Pixel | Analytics |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| AWS WAF Captcha | Security |
| Facebook Pixel | Analytics |
| Google Analytics | Analytics |
| Next.js 14.2.25 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Nginx | Web servers, Reverse proxies |
| React | JavaScript frameworks |
| RequireJS | JavaScript frameworks |
| Sentry 6.17.2 | Issue trackers |
| Snowplow Analytics | Analytics, IaaS |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Datadog | RUM, Analytics |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Lodash 4.17.21 | JavaScript libraries |
| Pinterest Conversion Tag | Analytics |
| Radix UI | UI frameworks |
| HSTS | Security |
| Transcend | Cookie compliance |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.eventbrite.de/ | csrftoken | Set-Cookie: .eventbrite.de |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.eventbrite.de/ | csrftoken, stableId | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: csrftoken=7dffa6f9c0ba4f819c2f8d89e9d9a1cc Set-Cookie: stableId=8e501d04-d6eb-4238-a101-b2f6c84adb8a |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2025-13465 | 6.9 | 0.00028 | 0.07863 | Lodash versions 4.0.0 through 4.17.22 are vulnerable to prototype pollution in the _.unset and _.omit functions. An attacker can pass crafted paths which cause Lodash to delete methods from global prototypes. The issue permits deletion of properties but does not allow overwriting their original behavior. This issue is patched on 4.17.23 |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.eventbrite.de/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
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
| URL | Evidence |
|---|---|
| https://www.eventbrite.de/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| TikTok Pixel | Analytics |
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| AWS WAF Captcha | Security |
| Facebook Pixel | Analytics |
| Google Analytics | Analytics |
| Next.js 14.2.25 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Nginx | Web servers, Reverse proxies |
| React | JavaScript frameworks |
| RequireJS | JavaScript frameworks |
| Sentry 6.17.2 | Issue trackers |
| Snowplow Analytics | Analytics, IaaS |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Datadog | RUM, Analytics |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Lodash 4.17.21 | JavaScript libraries |
| Pinterest Conversion Tag | Analytics |
| Radix UI | UI frameworks |
| HSTS | Security |
| Transcend | Cookie compliance |
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
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.eventbrite.de/ | 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 X-Content-Type-Options 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.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.eventbrite.de/l/legalterms/ | 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 Cookies: AS=b19edd83-43fd-4db5-882d-10b535f7c8fb G=v%3D2%26i%3Dd064bb94-1499-42ad-9e3e-72a475ad087b%26a%3D153e%26s%3D701d4bdbb3f4bd46c87be013a3d891ebd6... | Error message error report found in: |
Vulnerability description
We noticed that the target application does not properly handle exceptional conditions, leading to error messages that reveal sensitive information.
Risk description
The risk is that an attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application.
Recommendation
It is recommended treating all exceptions of the application flow. Ensure that error messages only contain minimal details.
Classification
| CWE | CWE-209 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.eventbrite.de/spectrum/ | 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 Cookies: AS=b19edd83-43fd-4db5-882d-10b535f7c8fb G=v%3D2%26i%3Dd064bb94-1499-42ad-9e3e-72a475ad087b%26a%3D153e%26s%3D701d4bdbb3f4bd46c87be013a3d891ebd6... |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-1377.awsdns-44.org, ns-2025.awsdns-61.co.uk, ns-229.awsdns-28.com, ns-972.awsdns-57.net
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.eventbrite.de | A | IPv4 address | 13.226.144.42 |
| www.eventbrite.de | A | IPv4 address | 13.226.144.120 |
| www.eventbrite.de | A | IPv4 address | 13.226.144.5 |
| www.eventbrite.de | A | IPv4 address | 13.226.144.6 |
| www.eventbrite.de | NS | Name server | ns-1377.awsdns-44.org |
| www.eventbrite.de | NS | Name server | ns-2025.awsdns-61.co.uk |
| www.eventbrite.de | NS | Name server | ns-229.awsdns-28.com |
| www.eventbrite.de | NS | Name server | ns-972.awsdns-57.net |
| www.eventbrite.de | SOA | Start of Authority | ns-229.awsdns-28.com. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
| www.eventbrite.de | CNAME | Canonical name | d3o36vj0gwxqjp.cloudfront.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.
Evidence
| Software / Version | Category |
|---|---|
| Next.js | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Sentry 6.17.2 | Issue trackers |
| Nginx | Web servers, Reverse proxies |
| React | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Snowplow Analytics | Analytics, IaaS |
| RequireJS | JavaScript frameworks |
| reCAPTCHA | Security |
| HSTS | Security |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Webpack | Miscellaneous |
| AWS WAF Captcha | Security |
| Google Tag Manager | Tag managers |
| PWA | 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
| Operating System | Accuracy |
|---|---|
| Crestron XPanel control system | 87% |
Vulnerability description
OS Detection