Vulnerability Scan Result
| Title: | Foods&Services | Soluciones Integrales en Abastecimiento Alimentario para Instituciones |
| Description: | No description found |
| ip_address | 160.153.0.160 |
| country | US  |
| network_name | Cloudflare London LLC |
| asn | AS209242 |
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 |
|---|---|
| HTTP/3 | Miscellaneous |
| Cloudflare | CDN |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| HTTP/3 | Miscellaneous |
| 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.
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
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
We found insecure DNS cookie usage on the following nameservers: ns13.domaincontrol.com, ns14.domaincontrol.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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| foodsandservice.com | TXT | Text record | "MS=ms29807246" |
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
| 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 6.8.3 | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| FitVids.JS 4.27.4 | Widgets, Video players |
| Divi 4.27.4 | Page builders, WordPress themes, WordPress plugins |
| Easy Pie Chart | JavaScript libraries |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| Clipboard.js | JavaScript libraries |
| Lodash 1.13.7 | JavaScript libraries |
| Google Font API | Font scripts |
| RSS | 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 |
|---|---|
| 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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-STABLE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| foodsandservice.com | A | IPv4 address | 160.153.0.160 |
| foodsandservice.com | NS | Name server | ns13.domaincontrol.com |
| foodsandservice.com | NS | Name server | ns14.domaincontrol.com |
| foodsandservice.com | MX | Mail server | 0 foodsandservice-com.mail.protection.outlook.com |
| foodsandservice.com | SOA | Start of Authority | ns13.domaincontrol.com. dns.jomax.net. 2025080501 28800 7200 604800 600 |
| foodsandservice.com | TXT | Text record | "MS=ms29807246" |
| foodsandservice.com | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -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
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| selector1 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1f2H+t8rm0zQEam6hJ2RvSL8pNRk77uEm1zJz/OxDMUTiyup7rmydmbGtTVh8+BOm0bQue9vthOWINWsl5fl/WIdF37/fczfEo0kiwMDnRRKZoJxN5hnoLbmF0kGKWqc9Rt1mBRH9LVJsE25u3sHorHV4Rlt2jL98g8BhVeySKtKPeZh3V+LppyE7eLOn5top" "3djkPHFHvfgT/of7MNtT6M3DUVE2xL5R2knANpfxZ/Bauanyn/Vy3n/yIFcTvjcGansgK5oKY0lttvEWw3Iz+GUrpuB38IhQAJlQomk+om60FbMc3h6Y65HMGizHS68C2Iz4S4KmdChyxYzK5qS3QIDAQAB;" |
| selector2 | rsa | 1422 | "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxFq344yDPjJ63y0rwEHOMqvFCahiF6JvFLaF0JrbsG0u/lp/EYDNVtuTNcLbys+9YQcqx/PI8aKpQ1Q/coZFAOUJGGvuPHpClx8eSERWm5j+JJ0gLW/uVmb69nWCAvJBG3gvZZDesOhnJQ/TNKvHkmbbN/21ZIOs6ZaNfDf2OE0imBdhCpeX5ofW+5b+AbFoZ" "yktd44p+lo9P8W7q5M2zRao02d43iQLZoaj6LGhX97n4aCTXbc8UIobwaa8u7Ve/MOqtkvzVKFF58JcL3/PaQWVUFIukT/f4erpzrNh6MuuK13YEgv/6rebCFzYvqD9/LmfBdI7+OskvsOAuEop1QIDAQAB;" |
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| foodsandservice.com | SPF | Sender Policy Framework | "v=spf1 include:spf.protection.outlook.com -all" |