Vulnerability Scan Result
| Title: | United Nations Economic and Social Commission for Western Asia |
| Description: | No description found |
| ip_address | 104.26.11.201 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.26.10.201 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 172.67.72.25 |
| 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 | https-alt | cloudflare - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Clipboard.js | JavaScript libraries |
| FancyBox 10.6.10 | JavaScript libraries |
| Flickity | JavaScript libraries |
| Adobe Fonts | Font scripts |
| Google Font API | Font scripts |
| Bootstrap 1.13.18 | UI frameworks |
| core-js 3.1.3 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Isotope | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Masonry | JavaScript libraries |
| Typed.js 10.6.10 | JavaScript libraries |
| AOS | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Plyr | Video players |
| Popper | Miscellaneous |
| Prism 10.6.10 | Miscellaneous |
| DoubleClick Floodlight | Advertising |
| Typekit | Font scripts |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| Drupal 10 | CMS |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
Web Application Vulnerabilities
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://unescwa.org/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Clipboard.js | JavaScript libraries |
| FancyBox 10.6.10 | JavaScript libraries |
| Flickity | JavaScript libraries |
| Adobe Fonts | Font scripts |
| Google Font API | Font scripts |
| Bootstrap 1.13.18 | UI frameworks |
| core-js 3.1.3 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Isotope | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| Masonry | JavaScript libraries |
| Typed.js 10.6.10 | JavaScript libraries |
| AOS | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Plyr | Video players |
| Popper | Miscellaneous |
| Prism 10.6.10 | Miscellaneous |
| DoubleClick Floodlight | Advertising |
| Typekit | Font scripts |
| WordPress | CMS, Blogs |
| Cloudflare | CDN |
| Drupal 10 | CMS |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| jsDelivr | 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://unescwa.org/ | Response headers include the HTTP Content-Security-Policy security header with the following security issues: |
Vulnerability description
We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.
Risk description
For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.
Recommendation
Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.
Classification
| CWE | CWE-1021 |
| 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 managed to detect that Drupal has reached the End-of-Life (EOL).
Version detected: 10 End-of-life date: 2023-12-15 Latest version for the cycle: 10.0.11 This release cycle (10.0) doesn't have long-term-support (LTS). The cycle was released on 2022-12-15 and its latest release date was 2023-09-19. The support ended on 2023-06-21.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
We managed to detect that Drupal has reached the End-of-Life (EOL).
Version detected: 10 End-of-life date: 2023-12-15 Latest version for the cycle: 10.0.11 This release cycle (10.0) doesn't have long-term-support (LTS). The cycle was released on 2022-12-15 and its latest release date was 2023-09-19. The support ended on 2023-06-21.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
We managed to detect that Drupal has reached the End-of-Life (EOL).
Version detected: 10 End-of-life date: 2023-12-15 Latest version for the cycle: 10.0.11 This release cycle (10.0) doesn't have long-term-support (LTS). The cycle was released on 2022-12-15 and its latest release date was 2023-09-19. The support ended on 2023-06-21.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| unescwa.org | TXT | Text record | "google-site-verification=7waiH3qVW9vk8cIYR-4tzHdABJ85YuM18PoX4AZkpL4" |
| unescwa.org | TXT | Text record | "google-site-verification=A7-8Ua7ZlnLha5eIbbMQMIYa2Ku375UlaRROHahEvxk" |
| unescwa.org | TXT | Text record | "google-site-verification=_7Ga_1yAW_Cr09HWKIFiT8Wn_sbEg4v_oCkGH_tolDY" |
| unescwa.org | TXT | Text record | "google-site-verification=lJwOXxOa-lvJsbsXVjhQtAbx9gp7Z9bmMgSQufNPZBg" |
Vulnerability description
We found that the target server has no DMARC policy configured. A missing DMARC (Domain-based Message Authentication, Reporting, and Conformance) policy means that the domain is not enforcing any DMARC policies to protect against email spoofing and phishing attacks. Without DMARC, even if SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail) are configured, there is no mechanism to tell receiving email servers how to handle messages that fail authentication. This leaves the domain vulnerable to abuse, such as email spoofing and impersonation.
Risk description
Without a DMARC policy, your domain is highly vulnerable to email spoofing, allowing attackers to impersonate your brand and send fraudulent emails that appear legitimate. This can lead to phishing attacks targeting your customers, employees, or partners, potentially resulting in stolen credentials, financial loss, or unauthorized access to sensitive systems. Additionally, repeated spoofing attempts can severely damage your brand's reputation, as recipients may lose trust in communications from your domain, associating your brand with malicious activity. The absence of DMARC also prevents you from monitoring and mitigating email-based attacks, leaving your domain exposed to ongoing abuse.
Recommendation
We recommend implementing a DMARC policy for your domain. Start by configuring a DMARC record with a policy of p=none, which will allow you to monitor email flows without impacting legitimate emails. This initial setup helps identify how emails from your domain are being processed by recipient servers. Once you’ve verified that legitimate emails are passing SPF and DKIM checks, you can gradually enforce stricter policies like p=quarantine or p=reject to protect against spoofing and phishing attacks. Additionally, include rua and ruf email addresses in the DMARC record to receive aggregate and forensic reports. These reports will provide valuable insights into authentication failures and help you detect any spoofing attempts.
Evidence
We managed to detect that Drupal has reached the End-of-Life (EOL).
Version detected: 10 End-of-life date: 2023-12-15 Latest version for the cycle: 10.0.11 This release cycle (10.0) doesn't have long-term-support (LTS). The cycle was released on 2022-12-15 and its latest release date was 2023-09-19. The support ended on 2023-06-21.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
We checked 2056 selectors but found no DKIM records.
Vulnerability description
We found that no DKIM record was configured. When a DKIM (DomainKeys Identified Mail) record is not present for a domain, it means that outgoing emails from that domain are not cryptographically signed. DKIM is a critical component of email authentication, allowing recipients to verify that an email was genuinely sent from an authorized server and that the message has not been altered in transit. The absence of a DKIM record leaves the domain vulnerable to email spoofing and phishing attacks, as attackers can send fraudulent emails that appear to originate from the domain without any cryptographic verification.
Risk description
Without a DKIM record, recipients have no way of verifying the integrity or authenticity of emails sent from the domain. This increases the likelihood of phishing and spoofing attacks, where malicious actors impersonate the domain to send fraudulent emails. This can lead to significant security incidents, such as credential theft, financial fraud, or the distribution of malware. Additionally, many email providers use DKIM as part of their spam and reputation filters, meaning that emails from a domain without DKIM may be flagged as spam or rejected, impacting the deliverability and reputation of legitimate emails.
Recommendation
We recommend implementing DKIM for your domain to enhance email security and protect your brand from email-based attacks. Generate a DKIM key pair (public and private keys), publish the public key in the DNS under the appropriate selector, and configure your email servers to sign outgoing messages using the private key. Ensure that the DKIM key length is at least 1024 bits to prevent cryptographic attacks. Regularly monitor DKIM signatures to ensure the system is functioning correctly and update keys periodically to maintain security.
Evidence
We found insecure DNS cookie usage on the following nameservers: autumn.ns.cloudflare.com, bill.ns.cloudflare.com
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
We managed to detect that Drupal has reached the End-of-Life (EOL).
Version detected: 10 End-of-life date: 2023-12-15 Latest version for the cycle: 10.0.11 This release cycle (10.0) doesn't have long-term-support (LTS). The cycle was released on 2022-12-15 and its latest release date was 2023-09-19. The support ended on 2023-06-21.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Software / Version | Category |
|---|---|
| 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 |
|---|---|
| WordPress | CMS, Blogs |
| Drupal 10 | CMS |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 1.13.18 | UI frameworks |
| Amazon Web Services | PaaS |
| Typekit | Font scripts |
| Typed.js 10.6.10 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| jsDelivr | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| FancyBox 10.6.10 | JavaScript libraries |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Adobe Fonts | Font scripts |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Cloudflare | CDN |
| Prism 10.6.10 | Miscellaneous |
| Popper | 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
| Software / Version | Category |
|---|---|
| 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 |
|---|---|
| WordPress | CMS, Blogs |
| Drupal 10 | CMS |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 1.13.18 | UI frameworks |
| Amazon Web Services | PaaS |
| Typekit | Font scripts |
| Typed.js 10.6.10 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| jsDelivr | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| FancyBox 10.6.10 | JavaScript libraries |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Adobe Fonts | Font scripts |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Cloudflare | CDN |
| Prism 10.6.10 | Miscellaneous |
| Popper | 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 | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| unescwa.org | A | IPv4 address | 104.26.10.201 |
| unescwa.org | A | IPv4 address | 172.67.72.25 |
| unescwa.org | A | IPv4 address | 104.26.11.201 |
| unescwa.org | NS | Name server | autumn.ns.cloudflare.com |
| unescwa.org | NS | Name server | bill.ns.cloudflare.com |
| unescwa.org | MX | Mail server | 0 onesmtp.un.org |
| unescwa.org | MX | Mail server | 0 smtp.secureserver.net |
| unescwa.org | MX | Mail server | 0 smtp.unescwa.org |
| unescwa.org | MX | Mail server | 0 smtp2.unescwa.org |
| unescwa.org | MX | Mail server | 10 mailstore1.secureserver.net |
| unescwa.org | SOA | Start of Authority | autumn.ns.cloudflare.com. dns.cloudflare.com. 2406647918 10000 2400 604800 1800 |
| unescwa.org | AAAA | IPv6 address | 2606:4700:20::681a:bc9 |
| unescwa.org | AAAA | IPv6 address | 2606:4700:20::ac43:4819 |
| unescwa.org | AAAA | IPv6 address | 2606:4700:20::681a:ac9 |
| unescwa.org | TXT | Text record | "google-site-verification=7waiH3qVW9vk8cIYR-4tzHdABJ85YuM18PoX4AZkpL4" |
| unescwa.org | TXT | Text record | "google-site-verification=A7-8Ua7ZlnLha5eIbbMQMIYa2Ku375UlaRROHahEvxk" |
| unescwa.org | TXT | Text record | "google-site-verification=_7Ga_1yAW_Cr09HWKIFiT8Wn_sbEg4v_oCkGH_tolDY" |
| unescwa.org | TXT | Text record | "google-site-verification=lJwOXxOa-lvJsbsXVjhQtAbx9gp7Z9bmMgSQufNPZBg" |
| unescwa.org | SPF | Sender Policy Framework | "v=spf1 mx -all" |
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 |
|---|---|---|---|
| unescwa.org | SPF | Sender Policy Framework | "v=spf1 mx -all" |
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Drupal 10 | CMS |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 1.13.18 | UI frameworks |
| Amazon Web Services | PaaS |
| Typekit | Font scripts |
| Typed.js 10.6.10 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| jsDelivr | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| FancyBox 10.6.10 | JavaScript libraries |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Adobe Fonts | Font scripts |
| reCAPTCHA | Security |
| DoubleClick Floodlight | Advertising |
| Cloudflare | CDN |
| Prism 10.6.10 | Miscellaneous |
| Popper | 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Drupal 10 | CMS |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 1.13.18 | UI frameworks |
| Amazon Web Services | PaaS |
| Typekit | Font scripts |
| Typed.js 10.6.10 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| jsDelivr | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| FancyBox 10.6.10 | JavaScript libraries |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Adobe Fonts | Font scripts |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Cloudflare | CDN |
| Prism 10.6.10 | Miscellaneous |
| Popper | Miscellaneous |
| Drupal Multisite | Hosting |
| 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
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Drupal 10 | CMS |
| MySQL | Databases |
| PHP | Programming languages |
| Bootstrap 1.13.18 | UI frameworks |
| Amazon Web Services | PaaS |
| Typekit | Font scripts |
| Typed.js 10.6.10 | JavaScript libraries |
| Modernizr | JavaScript libraries |
| MailChimp | Marketing automation, Email |
| jsDelivr | CDN |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| FancyBox 10.6.10 | JavaScript libraries |
| Cloudflare Browser Insights | Analytics, RUM |
| Clipboard.js | JavaScript libraries |
| Adobe Fonts | Font scripts |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Cloudflare | CDN |
| Prism 10.6.10 | Miscellaneous |
| Popper | 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
| Software / Version | Category |
|---|---|
| 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.