Vulnerability Scan Result
| Title: | BrickAI - AI-Powered Meta Advertising Platform |
| Description: | Create and manage Meta ad campaigns with AI-powered image generation. Designed for small businesses and non-technical users. |
| ip_address | 34.111.179.208 |
| country | US  |
| network_name | Google LLC |
| asn | AS396982 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Google Cloud Trace | Performance |
| D3 | JavaScript graphics |
| Express | Web frameworks, Web servers |
| Facebook Pixel 2.9.265 | Analytics |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| Lucide | Font scripts |
| Node.js | Programming languages |
| Open Graph | Miscellaneous |
| Plotly 3 | JavaScript graphics |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.trybrick.ai:443/ | GAESA | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: GAESA=Cp4BMDA1ZWI2OTc0YzM4NWIxNjAyYzYzNDdmNzI4N2U0ZDhlNTFhNjViMTUxZWY2ZjZjYzgxOGU0YmVjY2QzNTU2OTM5NmUzY2Q5OWZkOThiN2UyOTc0MWUwYjVjMmNiZWVhNTJkNjgzM2Y2MGYzMWYyMjg4ZDgyNDg3YThmMTRmZmJjNDk5MTkxZjk4ZjdkODM2ZWMyNTA4NWJhMzhmZjEQhNa04sYz |
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
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.trybrick.ai:443/ | GAESA | Set-Cookie: GAESA=Cp4BMDA1ZWI2OTc0YzM4NWIxNjAyYzYzNDdmNzI4N2U0ZDhlNTFhNjViMTUxZWY2ZjZjYzgxOGU0YmVjY2QzNTU2OTM5NmUzY2Q5OWZkOThiN2UyOTc0MWUwYjVjMmNiZWVhNTJkNjgzM2Y2MGYzMWYyMjg4ZDgyNDg3YThmMTRmZmJjNDk5MTkxZjk4ZjdkODM2ZWMyNTA4NWJhMzhmZjEQhNa04sYz |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| 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
| Software / Version | Category |
|---|---|
| Google Cloud | IaaS |
| Google Cloud CDN | CDN |
| Google Cloud Trace | Performance |
| D3 | JavaScript graphics |
| Express | Web frameworks, Web servers |
| Facebook Pixel 2.9.265 | Analytics |
| core-js 3.32.2 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| Lucide | Font scripts |
| Node.js | Programming languages |
| Open Graph | Miscellaneous |
| Plotly 3 | JavaScript graphics |
| Google Tag Manager | Tag managers |
| 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 | Evidence |
|---|---|
| https://www.trybrick.ai:443/ | 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 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.trybrick.ai:443/ | 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.trybrick.ai:443/ | 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 | Email Address: hi@trybrick.ai |
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 |
Infrastructure Vulnerabilities
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 7.0-STABLE | 90% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Node.js | Programming languages |
| Google Cloud | IaaS |
| Express | Web frameworks, Web servers |
| HSTS | Security |
| Google Cloud Trace | Performance |
| Google Cloud CDN | CDN |
| HTTP/3 | Miscellaneous |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Facebook Pixel 2.9.265 | Analytics |
| Google Font API | Font scripts |
| Open Graph | 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 |
|---|---|---|---|
| www.trybrick.ai | A | IPv4 address | 34.111.179.208 |
| www.trybrick.ai | TXT | Text record | "replit-verify=3a288ea9-20e4-4f8d-ad50-02959a0a0497" |
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.