Vulnerability Scan Result
| Title: | 5th Annual Cornhole Tournament | Yakima Rotaract (Powered by Donorbox) |
| Description: | No description found |
| ip_address | 104.18.23.83 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
| ip_address | 104.18.22.83 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
80/tcp | http | Cloudflare http proxy - |
443/tcp | https | cloudflare - |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
8080/tcp | http | Cloudflare http proxy - |
8443/tcp | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Donorbox | Fundraising & donations |
| Font Awesome | Font scripts |
| Froala Editor 2+ | Rich text editors |
| jQuery | JavaScript libraries |
| New Relic | RUM |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Sentry | Issue trackers |
| Stimulus | JavaScript frameworks |
| Stripe 3 | Payment processors |
| Turbo | Performance |
| PWA | Miscellaneous |
| Cloudflare | CDN |
| Heroku | PaaS |
| jsDelivr | CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://donorbox.org/events/777149/steps/choose_tickets | _donations_session | Set-Cookie: .donorbox.org |
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 | Evidence |
|---|---|
| https://donorbox.org/events/777149/steps/choose_tickets | 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
| Software / Version | Category |
|---|---|
| Donorbox | Fundraising & donations |
| Font Awesome | Font scripts |
| Froala Editor 2+ | Rich text editors |
| jQuery | JavaScript libraries |
| New Relic | RUM |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Sentry | Issue trackers |
| Stimulus | JavaScript frameworks |
| Stripe 3 | Payment processors |
| Turbo | Performance |
| PWA | Miscellaneous |
| Cloudflare | CDN |
| Heroku | PaaS |
| jsDelivr | CDN |
| 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
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
Vulnerability description
Website is accessible.
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.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.donorbox.org | TXT | Text record | "v=DMARC1;p=reject;pct=100;fo=1;rua=mailto:b99c706e@mxtoolbox.dmarc-report.com,mailto:postmaster@donorbox.org;ruf=mailto:b99c706e@forensics.dmarc-report.com" |
Vulnerability description
We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.
Risk description
Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.
Recommendation
To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| donorbox.org | A | IPv4 address | 104.18.22.83 |
| donorbox.org | A | IPv4 address | 104.18.23.83 |
| donorbox.org | NS | Name server | linda.ns.cloudflare.com |
| donorbox.org | NS | Name server | neil.ns.cloudflare.com |
| donorbox.org | MX | Mail server | 1 aspmx.l.google.com |
| donorbox.org | MX | Mail server | 10 alt3.aspmx.l.google.com |
| donorbox.org | MX | Mail server | 10 alt4.aspmx.l.google.com |
| donorbox.org | MX | Mail server | 5 alt1.aspmx.l.google.com |
| donorbox.org | MX | Mail server | 5 alt2.aspmx.l.google.com |
| donorbox.org | SOA | Start of Authority | linda.ns.cloudflare.com. dns.cloudflare.com. 2376187630 10000 2400 604800 1800 |
| donorbox.org | AAAA | IPv6 address | 2606:4700::6812:1653 |
| donorbox.org | AAAA | IPv6 address | 2606:4700::6812:1753 |
| donorbox.org | TXT | Text record | "1password-site-verification=62K7GIJBLVACJKGTDVI4RWH5VM" |
| donorbox.org | TXT | Text record | "apple-domain-verification=lVx6sbP9vaEUBmhk" |
| donorbox.org | TXT | Text record | "facebook-domain-verification=axwyha1qc6a2afbic713qlx755yjvo" |
| donorbox.org | TXT | Text record | "google-site-verification=-He0dWH11bOcOu_Oifq60ltpqu2ntIDss3tLgyb1f5Q" |
| donorbox.org | TXT | Text record | "google-site-verification=SG3AVJidJ9WCK1_Hbo3TF3aegcGBT9QBj7aYJyk2ZMs" |
| donorbox.org | TXT | Text record | "google-site-verification=nNXcErow3IbPzx0u29Kn3wgr1_BjcIkiVCghSH7Gheg" |
| donorbox.org | TXT | Text record | "google-site-verification=oWRPieQ30f8RNEMPBvuVn7FB8b7M6bmXne1rL0iw198" |
| donorbox.org | TXT | Text record | "google-site-verification=uCkVxjYXNHGNskjGIqcGb4RVkiVs_2QnbGb33XSfCww" |
| donorbox.org | TXT | Text record | "google-site-verification=yZ2BzbtU3aGH3Osxi85oB2MbkJi9S1uieJuHSIuQqJQ" |
| donorbox.org | TXT | Text record | "growsurf=u25p8w" |
| donorbox.org | TXT | Text record | "protonmail-verification=26ca0b0ebc2a024c15bf42f13e1928c01758dc9a" |
| donorbox.org | TXT | Text record | "prowly-verification=6365d1929d7fc2efc1a28eddbdb6fc452ba22cb47ef1ded4c3ffacc37876ea77" |
| donorbox.org | SPF | Sender Policy Framework | "v=spf1 redirect=donorbox.org.hosted.spf-report.com" |
| _dmarc.donorbox.org | TXT | Text record | "v=DMARC1;p=reject;pct=100;fo=1;rua=mailto:b99c706e@mxtoolbox.dmarc-report.com,mailto:postmaster@donorbox.org;ruf=mailto:b99c706e@forensics.dmarc-report.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.
Evidence
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.1-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| donorbox.org | SPF | Sender Policy Framework | "v=spf1 redirect=donorbox.org.hosted.spf-report.com" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuTrLGq925oZh5/Wm26rXnfiPrsO8trl4IynO5MpLW8hB3xv1BhOuAPDQ1xNYJT56WJ24mYTh4+jAgRB86GV10yLlOBVBf0HTa2ZlM74XJqyPkEu5Hlk7mf9+ip8FMnnzMAbL5pOWii/Y09xW9FT+9FB9sG1XCHTd+DXkuzl0FUvIWe/Ae5uvGC7vZFPUgwtvE" "dhaWUxkXmEpnr0AEaAgsNtjA/DKHcz+jvuE4u71Qlz7wrZhYphRdD01y6fgMVpuuZyHtLK3CUa2S/Oano3XBnC2B9v5DnOBEQGD7Bco6Bm6HZSYtnXG/KHSpaALoaDwVmPUVGQBiWIrqAFCmOlTbQIDAQAB" | |
| s2 | rsa | 1296 | "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCZ1LyIeH+/W4MEmcruv/SynuDWP6Z8dRy55S4XBzPbFSWzYut9bNjx6b53D/4gMZi3PVaG+m7V7hhb9EGJ49Z49NTazs/0mSj7h0dJ31YbHjl6cfIjcQlMiA/q36Zz9lRCz85oCYAW1FnDh9hZ6n6k7Uugr3OgKsucjDqJefJvfwIDAQAB" |
| s1 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAs6hPvUpde8Sky1Tt7GUiJMZ4MhD01RGpwR7CH5/udXFDH582v0fXSyNcxWaannGYq4O3Bbhct5Ul9wXIHWUVi46eAA/jDXtfdS/P7qqlwvpTYl/BngKvhT1MBZHjTrogrIqmbiXaIvK2fRhjahvUP7JsP4hlTy2NUU4pKwOV2ZZeaONHk6ks23Jo2hN8eDlRB55d+" "s4UvXAELKmUKmMRknhK/cFVzgMFB/6zqe012VIGMJ4qa19tRck1tSAZMD+LLa2vzzoBQ9ofIYn5/jVOkcuTu5XhEuxYBi8iOQGL0H0UG2FPS1/TjbEl62wNrphkfKSEP0BkJLQmoHVIGDiyfwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| Heroku | PaaS |
| Google Analytics | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
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
| Software / Version | Category |
|---|---|
| Heroku | PaaS |
| Google Analytics | Analytics |
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
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
| Software / Version | Category |
|---|---|
| Heroku | PaaS |
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
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
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare | CDN |
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
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare | CDN |
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
| Software / Version | Category |
|---|---|
| Heroku | PaaS |
| Cloudflare Browser Insights | Analytics, RUM |
| HSTS | Security |
| Cloudflare | CDN |
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
| Software / Version | Category |
|---|---|
| Cloudflare Browser Insights | Analytics, RUM |
| Cloudflare | CDN |
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.