Vulnerability Scan Result
| Title: | Just a moment... |
| Description: | No description found |
| ip_address | 185.16.44.89 |
| country | FR  |
| network_name | Planet Service SARL |
| asn | AS61168 |
No open ports were found.
| Software / Version | Category |
|---|---|
| Angular 18.2.13 | JavaScript frameworks |
| AT Internet Analyzer | Analytics |
| Linkedin Insight Tag | Analytics |
| Bootstrap 4.5.3 | UI frameworks |
| Zone.js | JavaScript frameworks |
| core-js 3.26.0 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| PHP | Programming languages |
| Piano | Personalisation |
| Piano Analytics | Analytics |
| Splide | JavaScript libraries |
| AB Tasty | A/B Testing |
| Cookie Control | Cookie compliance |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| Cookiebot 1 | Cookie compliance |
| DigiCert | SSL/TLS certificate authorities |
| Drupal 10 | CMS |
| Drupal Multisite | Hosting |
| Google Tag Manager | Tag managers |
| Lodash 4.17.21 | JavaScript libraries |
| HSTS | Security |
| TypeScript | Programming languages |
| Varnish | Caching |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| http://chronopost.fr/track | 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 |
|---|---|
| Angular 18.2.13 | JavaScript frameworks |
| AT Internet Analyzer | Analytics |
| Linkedin Insight Tag | Analytics |
| Bootstrap 4.5.3 | UI frameworks |
| Zone.js | JavaScript frameworks |
| core-js 3.26.0 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| PHP | Programming languages |
| Piano | Personalisation |
| Piano Analytics | Analytics |
| Splide | JavaScript libraries |
| AB Tasty | A/B Testing |
| Cookie Control | Cookie compliance |
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
| Cookiebot 1 | Cookie compliance |
| DigiCert | SSL/TLS certificate authorities |
| Drupal 10 | CMS |
| Drupal Multisite | Hosting |
| Google Tag Manager | Tag managers |
| Lodash 4.17.21 | JavaScript libraries |
| HSTS | Security |
| TypeScript | Programming languages |
| Varnish | Caching |
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.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: c.ns.domainoo.fr, a.ns.domainoo.fr, d.ns.domainoo.fr, b.ns.domainoo.fr
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 |
|---|---|---|---|
| chronopost.fr | A | IPv4 address | 185.16.44.89 |
| chronopost.fr | NS | Name server | c.ns.domainoo.fr |
| chronopost.fr | NS | Name server | a.ns.domainoo.fr |
| chronopost.fr | NS | Name server | d.ns.domainoo.fr |
| chronopost.fr | NS | Name server | b.ns.domainoo.fr |
| chronopost.fr | MX | Mail server | 10 mxa-00379001.gslb.pphosted.com |
| chronopost.fr | MX | Mail server | 10 mxb-00379001.gslb.pphosted.com |
| chronopost.fr | SOA | Start of Authority | a.ns.domainoo.fr. postmaster.domainoo.com. 2026012802 14400 3600 1209600 86400 |
| chronopost.fr | TXT | Text record | "google-site-verification=CsCR50mGE-CDa49xtG00DJ1KosDbzMhfA3OEIef9QBs" |
| chronopost.fr | TXT | Text record | "google-site-verification=GRq0OxoqtnTEhkU3F_pTnZvEYq6Q73BS0gaYfz_7JLU" |
| chronopost.fr | TXT | Text record | "MS=2E54C7AA94DD8216E7BF0797FAC05762C632E81D" |
| chronopost.fr | TXT | Text record | "google-site-verification=GXDJhcBTmo5vI6feD_XVO7HyVkmMuwQ0wu1iH4Hlkcs" |
| chronopost.fr | TXT | Text record | "docusign=c2412e7a-249c-4ba8-8a86-3abf65750b43" |
| chronopost.fr | TXT | Text record | "_0smqesjab2fj9mgm7begyecirl2jfiz" |
| chronopost.fr | TXT | Text record | "google-site-verification=9wBSI0rqtllG0zzML_QPSrXv5g85XcNsSW6LRtRLxiM" |
| chronopost.fr | TXT | Text record | "google-site-verification=a7sBTO0sqdivVdn9lXfMqyE_QON32uDpaocffQHnuTY" |
| chronopost.fr | TXT | Text record | "google-site-verification=suLrXV4HRT2JwWAgugcMR6N_cYmpAtGDIgdxylkMeQw" |
| chronopost.fr | TXT | Text record | "_6hp05wa62bpobzyb5pozued8ttt4yyj" |
| chronopost.fr | SPF | Sender Policy Framework | "v=spf1 mx include:_spf.chronopost.fr include:_spf.salesforce.com include:_spf.google.com include:spf-customer.sindup.net ~all" |
| _dmarc.chronopost.fr | TXT | Text record | "v=DMARC1; p=reject; sp=reject; rua=mailto:dsi.rua.dmarc@chronopost.fr,mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dsi.ruf.dmarc@chronopost.fr,mailto:dmarc_ruf@emaildefense.proofpoint.com; rf=afrf; pct=100; ri=86400; adkim=r; aspf=r; fo=1" |
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.