Vulnerability Scan Result
| Title: | Home | Mastercard Foundation |
| Description: | The Mastercard Foundation works with visionary organizations to enable young people in Africa and in Indigenous communities in Canada to access dignified and fulfilling work. |
| ip_address | 3.33.186.135 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 15.197.167.90 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | Netlify - |
443/tcp | https | Netlify - |
| Software / Version | Category |
|---|---|
| Twitter Ads | Advertising |
| Alpine.js | JavaScript frameworks |
| Linkedin Insight Tag | Analytics |
| ButterCMS | CMS |
| Flickity 2 | JavaScript libraries |
| Google Analytics | Analytics |
| Open Graph | Miscellaneous |
| Unpkg | CDN |
| PWA | Miscellaneous |
| ActiveCampaign | Marketing automation, Email |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Netlify | PaaS, CDN |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://mastercardfdn.org/en/ | 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 |
|---|---|
| Twitter Ads | Advertising |
| Alpine.js | JavaScript frameworks |
| Linkedin Insight Tag | Analytics |
| ButterCMS | CMS |
| Flickity 2 | JavaScript libraries |
| Google Analytics | Analytics |
| Open Graph | Miscellaneous |
| Unpkg | CDN |
| PWA | Miscellaneous |
| ActiveCampaign | Marketing automation, Email |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Netlify | PaaS, 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
| URL | Evidence |
|---|---|
| https://mastercardfdn.org/en/ | 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
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://mastercardfdn.org/en/ | 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 |
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.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://mastercardfdn.org/en/ | 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: mcfghanaalumninetwork@gmail.com mcfsenegalalumninetwork@gmail.com osouloy@mastercardfdn.org jmaheshwari@momentus.global autumn@kglfwd.com aida@batongafoundation.org urusaro@kglfwd.com smcgeachin@mastercardfdn.org adiop@meda.org rnandelenga@mastercardfdn.org ttiemens@mastercardfdn.org hi-innovator@nssfug.org stephanie@batongafoundation.org mcfkenyaalumninetwork@gmail.com mcfrwandaalumninetwork@gmail.com |
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
We found insecure DNS cookie usage on the following nameservers: ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone, ha4.markmonitor.zone
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 |
|---|---|---|---|
| _dmarc.mastercardfdn.org | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; adkim=s; aspf=s;" |
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 |
|---|---|---|---|
| _dmarc.mastercardfdn.org | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; adkim=s; aspf=s;" |
Vulnerability description
We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.
Risk description
Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.
Recommendation
We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| selector1 | rsa | 1296 | "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCnsSRjpHR8T30HYMZBSYgYGz16tfrDMKdKfJUWiySURc4d31pMiyYMFDklB1BMZzkyR9aCmCOH2LbZT5I+PyoDOT3W7P/ZQ69u3ig7YNW/vNPkCGtBEjPDjzoGyGwrvIbyCizUMHgn4xrPM1ouhNKu2uihJC6ZZ1i4JXsU4SnMSwIDAQAB; n=1024,1449887925,1" "465699125" |
Evidence
| Software / Version | Category |
|---|---|
| Alpine.js | JavaScript frameworks |
| Unpkg | CDN |
| Flickity 2 | JavaScript libraries |
| Twitter Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| ActiveCampaign | Marketing automation, Email |
| reCAPTCHA | Security |
| Netlify | PaaS, 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
| Operating System | Accuracy |
|---|---|
| Android 5.0.1 | 90% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mastercardfdn.org | A | IPv4 address | 3.33.186.135 |
| mastercardfdn.org | A | IPv4 address | 15.197.167.90 |
| mastercardfdn.org | NS | Name server | ha1.markmonitor.zone |
| mastercardfdn.org | NS | Name server | ha2.markmonitor.zone |
| mastercardfdn.org | NS | Name server | ha3.markmonitor.zone |
| mastercardfdn.org | NS | Name server | ha4.markmonitor.zone |
| mastercardfdn.org | MX | Mail server | 10 mastercardfdn-org.mail.protection.outlook.com |
| mastercardfdn.org | SOA | Start of Authority | ha1.markmonitor.zone. hostmaster.markmonitor.com. 2025120201 86400 3600 2592000 172800 |
| mastercardfdn.org | TXT | Text record | "MS=ms92505148" |
| mastercardfdn.org | TXT | Text record | "v=verifydomain MS=4256722" |
| mastercardfdn.org | TXT | Text record | "v=verifydomain MS=9470589" |
| mastercardfdn.org | TXT | Text record | "apple-domain-verification=zhLbv7WB9lsU6fjS" |
| mastercardfdn.org | TXT | Text record | "v=verifydomain MS=1103905" |
| mastercardfdn.org | TXT | Text record | "MS=ms36574010" |
| mastercardfdn.org | TXT | Text record | "MS=ms75294527" |
| mastercardfdn.org | TXT | Text record | "v=verifydomain MS=2041693" |
| mastercardfdn.org | TXT | Text record | "include:spf-us.emailsignatures365.com" |
| mastercardfdn.org | TXT | Text record | "uif+2tJDSnM7fTItW8PGCnuILoUwaDTHJKNPoTIpPdlfUiikmD052wCJMikm4ma83AzdCG0LHSGRAeHjVZoNTw==" |
| mastercardfdn.org | TXT | Text record | "v=verifydomain MS=5259302" |
| mastercardfdn.org | TXT | Text record | "canva-site-verification=_NW_E6mp2yyE40KVUt_DVA" |
| mastercardfdn.org | TXT | Text record | "spf.ca.exclaimer.net" |
| mastercardfdn.org | TXT | Text record | "ZOOM_verify_23EcP8flSCme2VqOqiaTjw" |
| mastercardfdn.org | TXT | Text record | "docusign=c4a78df8-6da8-4cbe-a6c7-047be35995e1" |
| mastercardfdn.org | TXT | Text record | "28kctls18ia1h17adkg1qb1fvl" |
| mastercardfdn.org | TXT | Text record | "google-site-verification=TSCe8aPvWbK-n9zwPSQ3hVnHXGXil31Mb8F3R_0rK3o" |
| mastercardfdn.org | SPF | Sender Policy Framework | "v=spf1 ip4:4.205.197.91 ip4:192.254.121.248 include:spf.protection.outlook.com include:_phishspf.knowbe4.com include:spf.redpoints.com include:spf-us.emailsignatures365.com -all" |
| _dmarc.mastercardfdn.org | TXT | Text record | "v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email; adkim=s; aspf=s;" |
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| mastercardfdn.org | SPF | Sender Policy Framework | "v=spf1 ip4:4.205.197.91 ip4:192.254.121.248 include:spf.protection.outlook.com include:_phishspf.knowbe4.com include:spf.redpoints.com include:spf-us.emailsignatures365.com -all" |