Vulnerability Scan Result
| Title: | Login – agh3 Cloud |
| Description: | No description found |
| ip_address | 173.9.196.20 |
| country | US  |
| network_name | Comcast Cable Communications LLC |
| asn | AS7922 |
25/tcp | smtp | - - |
80/tcp | http | Microsoft HTTPAPI httpd 2 |
443/tcp | https | openresty - |
465/tcp | smtps | - - |
587/tcp | submission | - - |
993/tcp | imap | hMailServer imapd - |
995/tcp | pop3 | hMailServer pop3d - |
No technologies could be detected.
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://cloud.agh3.com/index.php/login | 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
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
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| cloud.agh3.com | SPF | Sender Policy Framework | "v=spf1 a ip4:69.209.87.37 ip4:173.9.196.30 ip4:173.9.196.20 ip4:12.40.75.138 ip4:74.217.1.14 ip4:198.144.177.78 include:emailsrvr.com include:_spf.google.com include:spf.protection.outlook.com ~all" |
Vulnerability description
We found that the Sender Policy Framework (SPF) record for the domain is configured with ~all (soft fail), which indicates that emails from unauthorized IP addresses are not explicitly denied. Instead, the recipient mail server is instructed to treat these messages with suspicion but may still accept them. This configuration may not provide enough protection against email spoofing and unauthorized email delivery, leaving the domain more vulnerable to impersonation attempts.
Risk description
The ~all directive in an SPF record allows unauthorized emails to pass through some email servers, even though they fail SPF verification. While such emails may be marked as suspicious or placed into a spam folder, not all mail servers handle soft fail conditions consistently. This creates a risk that malicious actors can spoof the domain to send phishing emails or other fraudulent communications, potentially causing damage to the organization's reputation and leading to successful social engineering attacks.
Recommendation
We recommend changing the SPF record's ~all (soft fail) directive to -all (hard fail). The -all setting tells recipient mail servers to reject emails from any IP addresses not listed in the SPF record, providing stronger protection against email spoofing. Ensure that all legitimate IP addresses and services that send emails on behalf of your domain are properly included in the SPF record before implementing this change.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns0.dnsmadeeasy.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 |
|---|---|
| Microsoft Windows XP SP3 | 85% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| OpenResty | Web servers |
| HSTS | Security |
| Nextcloud | Digital asset management, Miscellaneous |
| PWA | 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 |
|---|---|---|---|
| cloud.agh3.com | A | IPv4 address | 173.9.196.20 |
| cloud.agh3.com | NS | Name server | ns3.dnsmadeeasy.com |
| cloud.agh3.com | NS | Name server | ns4.dnsmadeeasy.com |
| cloud.agh3.com | NS | Name server | ns2.dnsmadeeasy.com |
| cloud.agh3.com | NS | Name server | ns1.dnsmadeeasy.com |
| cloud.agh3.com | NS | Name server | ns0.dnsmadeeasy.com |
| cloud.agh3.com | MX | Mail server | 20 alt1.aspmx.l.google.com |
| cloud.agh3.com | MX | Mail server | 10 aspmx.l.google.com |
| cloud.agh3.com | MX | Mail server | 20 alt2.aspmx.l.google.com |
| cloud.agh3.com | MX | Mail server | 30 aspmx2.googlemail.com |
| cloud.agh3.com | MX | Mail server | 30 aspmx3.googlemail.com |
| cloud.agh3.com | SOA | Start of Authority | ns0.dnsmadeeasy.com. dns.dnsmadeeasy.com. 2008015101 43200 3600 1209600 180 |
| cloud.agh3.com | TXT | Text record | "MS=ms35123514" |
| cloud.agh3.com | TXT | Text record | "google-site-verification=HpUKjz3Y8TE_mTmXv2QjkrhrQ6j9uFB7N1j_Rwi3sc4" |
| cloud.agh3.com | SPF | Sender Policy Framework | "v=spf1 a ip4:69.209.87.37 ip4:173.9.196.30 ip4:173.9.196.20 ip4:12.40.75.138 ip4:74.217.1.14 ip4:198.144.177.78 include:emailsrvr.com include:_spf.google.com include:spf.protection.outlook.com ~all" |
| cloud.agh3.com | CNAME | Canonical name | agh3.com |
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 |
|---|---|
| Microsoft HTTPAPI 2.0 | Web servers |
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.