Vulnerability Scan Result
| Title: | CDG Développement – Acteur du développement territorial |
| Description: | CDG Développement, filiale de la Caisse de Dépôt et de Gestion, est un opérateur et investisseur engagé dans le développement territorial du Maroc. Alliant innovation, performance et utilité collective, elle pilote des projets structurants pour un avenir durable et prospère. |
| ip_address | 52.18.119.66 |
| country | IE  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
22/tcp | ssh | OpenSSH 8.9p1 Ubuntu 3ubuntu0.13 |
80/tcp | http | Golang net/http server - |
443/tcp | https | Golang net/http server - |
| Software / Version | Category |
|---|---|
| Emotion | JavaScript frameworks, Development |
| Google Analytics | Analytics |
| Next.js 14.2.35 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Tailwind CSS | UI frameworks |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| AMP | JavaScript frameworks |
| Drupal | CMS |
| Google Tag Manager | Tag managers |
| HSTS | Security |
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://cdgdev.ma/_next/static/css/ | 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://cdgdev.ma/_next/static/css/ | 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 | Evidence |
|---|---|
| https://cdgdev.ma/_next/static/css/ | 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
| URL | Evidence |
|---|---|
| https://cdgdev.ma/ | 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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Emotion | JavaScript frameworks, Development |
| Google Analytics | Analytics |
| Next.js 14.2.35 | JavaScript frameworks, Web frameworks, Web servers, Static site generator |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| Tailwind CSS | UI frameworks |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Priority Hints | Performance |
| AMP | JavaScript frameworks |
| Drupal | CMS |
| 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
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://cdgdev.ma/ | 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 | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.cdgdev.ma | TXT | Text record | "v=DMARC1; p=none; fo=1; rua=mailto:security.assessment@cdgdev.ma; ruf=mailto:security.assessment@cdgdev.ma" |
Vulnerability description
We found that the target uses p=none in the DMARC policy. The DMARC policy set to p=none means that the domain owner is not taking any action on emails that fail DMARC validation. This configuration effectively disables enforcement, allowing potentially spoofed or fraudulent emails to be delivered without any additional scrutiny.
Risk description
Emails that fail DMARC checks are still delivered to recipients. This leaves the domain highly vulnerable to email spoofing and phishing attacks, as malicious actors can impersonate the domain without facing any consequences from DMARC enforcement.
Recommendation
We recommend changing the DMARC policy to p=quarantine or, ideally, p=reject to actively block or quarantine emails that fail DMARC validation. This will enhance the security of your domain against spoofing and phishing attacks by ensuring that only legitimate emails are delivered.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.cdgdev.ma | TXT | Text record | "v=DMARC1; p=none; fo=1; rua=mailto:security.assessment@cdgdev.ma; ruf=mailto:security.assessment@cdgdev.ma" |
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
| Operating System | Accuracy |
|---|---|
| Linux 2.6.32 | 93% |
Vulnerability description
OS Detection
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| selector1 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvVKZfMkCSHTGmhYMP6WxUuxQ2VJRfs40z5fcbIOytOEVSazaL1xfHvR/fgRJPxM32HSfDTQV61YtcASnXmQSGNGrDP6utlGKoWK0aKpi8xsqm7QxgGQKwiC2DjwqgdMMvNSsiHs+h2eogAd9PWZqEY1zFGTNT8lMVgVA8f4ZG5g2To515v7REv3j7twtQbrlq" "lQZEy3QN6iHKpdLrQS3t4psr0K/7UP/jW+iB4Yyi7ViX5xaEZa4BVUaNtmdx0/9TgqfmZpJMO9p4BHQQICgqSMitO2FsZU13cH3AuDnaGsUrvERBAB7UOhLalIbD8JrE9jXqleZ99klYnFz9nK5eQIDAQAB;" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| cdgdev.ma | A | IPv4 address | 52.18.119.66 |
| cdgdev.ma | NS | Name server | loukos2.wanacorp.com |
| cdgdev.ma | NS | Name server | ns2.wanamaroc.com |
| cdgdev.ma | NS | Name server | ns3.wanamaroc.com |
| cdgdev.ma | MX | Mail server | 20 mail2.cdgdev.ma |
| cdgdev.ma | MX | Mail server | 10 mail.cdgdev.ma |
| cdgdev.ma | MX | Mail server | 0 cdgdev-ma.mail.protection.outlook.com |
| cdgdev.ma | SOA | Start of Authority | ns2.wanamaroc.com. hostmaster.wanadoo.ma. 2007020738 7200 3600 604800 3600 |
| cdgdev.ma | TXT | Text record | "MS=ms66666650" |
| cdgdev.ma | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |
| _dmarc.cdgdev.ma | TXT | Text record | "v=DMARC1; p=none; fo=1; rua=mailto:security.assessment@cdgdev.ma; ruf=mailto:security.assessment@cdgdev.ma" |
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 |
|---|---|
| Drupal | CMS |
| PHP | Programming languages |
| Tailwind CSS | UI frameworks |
| AMP | JavaScript frameworks |
| HSTS | Security |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
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 |
|---|---|---|---|
| cdgdev.ma | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |