Vulnerability Scan Result
| Title: | National Site Materials Fargo, North Dakota | Site Materials Delivered Locally. Call 855-942-3433 Toll Free. |
| Description: | We Deliver in Fargo, North Dakota - When you need an aggregate supplier you can count on, you need National Site Materials. Gravel Fill, Dirt Top, Soil, Concrete, Building Blocks Products, Concrete Mix Material, Rebar, Precast Concrete Products, Asphalt & Paving Materials, Sand, Clay & Hardpan, River Rock, Lime Rock, Crushed Recycle Concrete, Rip Rap, Manure. |
| ip_address | 172.67.220.215 |
| country | - |
| network_name | Cloudflare, Inc. |
| asn | AS13335 |
| ip_address | 104.21.24.215 |
| 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 | http | cloudflare - |
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Clipboard.js | JavaScript libraries |
| GeneratePress 3.6.1 | WordPress themes |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| Redis | Databases |
| Underscore.js 1.13.7 | JavaScript libraries |
| Usercentrics | Cookie compliance |
| WordPress 6.9 | CMS, Blogs |
| WordPress Multisite | Hosting |
| Redis Object Cache | Caching |
| AMP | JavaScript frameworks |
| Cloudflare | CDN |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| RSS | Miscellaneous |
| Cart Functionality | Ecommerce |
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://fargositematerials.com/wp-login.php | 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
| URL | Evidence |
|---|---|
| https://fargositematerials.com/ | 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 |
|---|---|
| Microsoft Advertising | Advertising |
| Clipboard.js | JavaScript libraries |
| GeneratePress 3.6.1 | WordPress themes |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| Google Font API | Font scripts |
| HTTP/3 | Miscellaneous |
| jQuery 3.7.1 | JavaScript libraries |
| MySQL | Databases |
| PHP | Programming languages |
| Redis | Databases |
| Underscore.js 1.13.7 | JavaScript libraries |
| Usercentrics | Cookie compliance |
| WordPress 6.9 | CMS, Blogs |
| WordPress Multisite | Hosting |
| Redis Object Cache | Caching |
| AMP | JavaScript frameworks |
| Cloudflare | CDN |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| RSS | Miscellaneous |
| Cart Functionality | Ecommerce |
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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://fargositematerials.com/wp-json/oembed/1.0/embed | GET | Query: format=xml url=https://fargositematerials.com/ 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 | Possible API endpoint found at |
Vulnerability description
We found API endpoints while crawling the given web application.
Risk description
These endpoints may represent an attack surface for malicious actors interested in API-specific vulnerabilities.
Recommendation
Use the API Scanner to perform a more thorough vulnerability check for these endpoints, if an API specification is present.
Evidence
| URL | Evidence |
|---|---|
| https://fargositematerials.com/wp-login.php |
|
Vulnerability description
We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.
Risk description
The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.
Recommendation
Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.
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: jason.ns.cloudflare.com, nelly.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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.1-STABLE | 91% |
Vulnerability description
OS Detection
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
| Software / Version | Category |
|---|---|
| WordPress 6.9 | CMS, Blogs |
| Redis | Databases |
| MySQL | Databases |
| PHP | Programming languages |
| Redis Object Cache | Caching |
| GeneratePress 3.6.1 | WordPress themes |
| WordPress Multisite | Hosting |
| Usercentrics | Cookie compliance |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Google AdSense | Advertising |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | 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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| fargositematerials.com | A | IPv4 address | 104.21.24.215 |
| fargositematerials.com | A | IPv4 address | 172.67.220.215 |
| fargositematerials.com | NS | Name server | jason.ns.cloudflare.com |
| fargositematerials.com | NS | Name server | nelly.ns.cloudflare.com |
| fargositematerials.com | SOA | Start of Authority | jason.ns.cloudflare.com. dns.cloudflare.com. 2394943437 10000 2400 604800 1800 |
| fargositematerials.com | AAAA | IPv6 address | 2606:4700:3036::6815:18d7 |
| fargositematerials.com | AAAA | IPv6 address | 2606:4700:3030::ac43:dcd7 |
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 |
|---|---|
| WordPress 6.9 | CMS, Blogs |
| Cart Functionality | Ecommerce |
| Redis | Databases |
| MySQL | Databases |
| PHP | Programming languages |
| Redis Object Cache | Caching |
| GeneratePress 3.6.1 | WordPress themes |
| WordPress Multisite | Hosting |
| Usercentrics | Cookie compliance |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| jQuery | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| Google AdSense | Advertising |
| HSTS | Security |
| Cloudflare | CDN |
| HTTP/3 | Miscellaneous |
| 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.