Vulnerability Scan Result
| Title: | Attention Required! | Cloudflare |
| Description: | No description found |
| IP address | 172.64.144.79 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
| IP address | 104.18.43.177 |
| Country | - |
| AS number | AS13335 |
| Net name | Cloudflare Inc |
2082/tcp | http | Cloudflare http proxy - |
2083/tcp | https | nginx - |
2086/tcp | http | Cloudflare http proxy - |
2087/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| Cloudflare Bot Management | Security |
Web Application Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare | CDN |
| Cloudflare Bot Management | 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.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
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.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| bws.com.au | SPF | Sender Policy Framework | "v=spf1 ip4:40.127.76.156 ip4:20.53.235.172 ip4:203.36.225.251 ip4:203.36.225.254 ip4:203.36.225.249 ip4:203.36.225.250 ip4:203.26.178.149 ip4:203.36.225.252 ip4:199.102.178.221/30 ip4:199.102.178.224/29 ip4:199.102.178.241/29 ip4:199.102.178.248 ip4:168.1" "28.34.118 ip4:168.128.50.101 ip4:20.53.112.216 ip4:23.101.249.58 include:_spf.google.com include:mail.zendesk.com include:id.ngcomms.net ~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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| bws.com.au | A | IPv4 address | 172.64.144.79 |
| bws.com.au | A | IPv4 address | 104.18.43.177 |
| bws.com.au | NS | Name server | cortney.ns.cloudflare.com |
| bws.com.au | NS | Name server | sevki.ns.cloudflare.com |
| bws.com.au | MX | Mail server | 10 mailstream-australia-primary.area1.cloudflare.net |
| bws.com.au | MX | Mail server | 5 mailstream-syd.area1.cloudflare.net |
| bws.com.au | SOA | Start of Authority | cortney.ns.cloudflare.com. dns.cloudflare.com. 2373342504 10000 2400 604800 1800 |
| bws.com.au | TXT | Text record | "18f9812e-a07c-46df-8130-ce83e0fa0b1d" |
| bws.com.au | TXT | Text record | "210d7d74-58fc-4d34-b45e-5cb54b549c88" |
| bws.com.au | TXT | Text record | "2f2c4011-c1dd-4d22-a739-7499c52085d1" |
| bws.com.au | TXT | Text record | "466eb80a-a524-43d1-b632-ca0339b20c0c" |
| bws.com.au | TXT | Text record | "47981258-0ceb-4f1c-8c14-b698a0883457" |
| bws.com.au | TXT | Text record | "53108472-beed-4795-84a9-12fee868be2b \"'\"" |
| bws.com.au | TXT | Text record | "608d6d2f-abed-4c50-9bc9-0084a63eab47" |
| bws.com.au | TXT | Text record | "MS=ms55220806" |
| bws.com.au | TXT | Text record | "MS=ms84770247" |
| bws.com.au | TXT | Text record | "adobe-idp-site-verification=13e849cec7c7fbdc0330a534ba4610cb9e0de1de924b5f7ec83e9dd92176ef24" |
| bws.com.au | TXT | Text record | "apple-domain-verification=y0E6iVm5D6taH3jJ" |
| bws.com.au | TXT | Text record | "b36289b6-9a7c-4470-8795-b6d81f8b999c" |
| bws.com.au | TXT | Text record | "bwsprdui.azurewebsites.net" |
| bws.com.au | TXT | Text record | "d9146aac-7ff7-4f2e-8608-9d050608c066" |
| bws.com.au | TXT | Text record | "docusign=656706ba-3366-4f46-9814-5fd54d6bf537" |
| bws.com.au | TXT | Text record | "ea572b6d-ef68-4a24-ab00-72f9b12d113b" |
| bws.com.au | TXT | Text record | "facebook-domain-verification=8xxoel5t4r3odj8tove68upps2uvkd" |
| bws.com.au | TXT | Text record | "google-site-verification=0ZiJbu_-zB3AOyx26Z_h5ovBvUW2yDX0mP3GHwqVrJY" |
| bws.com.au | TXT | Text record | "google-site-verification=U_WVGRbn8l0Q5_V_XnQoSzoFrI5iKR2oMj-E8edaAIA" |
| bws.com.au | TXT | Text record | "google-site-verification=vY1VttAfqJxEvzrFokqEJ4WuL1DEKlqDbhnxZ9WIvvU" |
| bws.com.au | TXT | Text record | "have-i-been-pwned-verification=dweb_ncte4k2y7wdhoitm7viujea4" |
| bws.com.au | TXT | Text record | "ibmid=2a570a6d-a127-4a3c-8d00-0bc4268a24c6" |
| bws.com.au | TXT | Text record | "miro-verification=1ee7adf188b19ac5cbc9ba45cc9e81b570373b09" |
| bws.com.au | TXT | Text record | "onetrust-domain-verification=d963a4ca163e4861af73f225ccefb1f0" |
| bws.com.au | TXT | Text record | "twilio-domain-verification=ccd429b3d01b2a49be707d972a5f5907" |
| bws.com.au | TXT | Text record | "uber-domain-verification=431895a6-827c-49b5-a75c-2881af49a077" |
| bws.com.au | TXT | Text record | "uber-domain-verification=4da262b1-f70e-459a-aff0-311cea231c97" |
| bws.com.au | SPF | Sender Policy Framework | "v=spf1 ip4:40.127.76.156 ip4:20.53.235.172 ip4:203.36.225.251 ip4:203.36.225.254 ip4:203.36.225.249 ip4:203.36.225.250 ip4:203.26.178.149 ip4:203.36.225.252 ip4:199.102.178.221/30 ip4:199.102.178.224/29 ip4:199.102.178.241/29 ip4:199.102.178.248 ip4:168.1" "28.34.118 ip4:168.128.50.101 ip4:20.53.112.216 ip4:23.101.249.58 include:_spf.google.com include:mail.zendesk.com include:id.ngcomms.net ~all" |
| _dmarc.bws.com.au | TXT | Text record | "v=DMARC1; p=reject; sp=reject; pct=100; fo=1; rua=mailto:55062184c7d942baaff1722028fecf9d@dmarc-reports.cloudflare.net; ruf=mailto:ruf.bws@bws.com.au" |
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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 91% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| _dmarc.bws.com.au | TXT | Text record | "v=DMARC1; p=reject; sp=reject; pct=100; fo=1; rua=mailto:55062184c7d942baaff1722028fecf9d@dmarc-reports.cloudflare.net; ruf=mailto:ruf.bws@bws.com.au" |
Evidence
| DKIM selector | Key type | Key size | Value |
|---|---|---|---|
| s2 | rsa | 1296 | "k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDU4gYQxvqiEMHhtgRsUBrgY/+wXWhfbvMd4WR5nOQYN/eHJVZRLpMnJ7DBI/E2JkWw6LSrs/A0ZG+3BXaAaXlQudeeRfA/0XQGYdVOgcqOugOKDvGiBeB8fH/0G3RCCCyOA7BFokVimyNcajHzgjwCX4M0YgoVCF2JDIUuS8bu5QIDAQAB" |
| s1 | rsa | 1446 | "k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoM8Ul/fGaMWkd+2jF8ZJC1K+3Tajfq3mnXwzNhmFK+KWXk87ut/mU/ruRNE40TnaUmtaJhHti0zCyx/IcC4F9M566GrGjTF8eSBe8msSNJ/SfR2VrYwBh4YFe/C3Pvw/kgVzeuBNBLQ+6hlPwIYDD6Ayyqwz7fSrxrAj80yh/Ep21nw5pOT0FXbdhn1gMg4/KIPtu" "bLc2jfnN32bqDyRca01YQYOEd+TfUj1sYKOQDvXTSt8B5iihY62zEygjHjP9kmzUAlyJaNxYoOTmUHZpS6lCSz5eEvuki29ojfF0CEpMsamIf3FMwtJqydshalt2Ty+lr8TOlwoI6kRmeWiJwIDAQAB" |
Evidence
| Software / Version | Category |
|---|---|
| Cloudflare Bot Management | Security |
| 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 Bot Management | Security |
| 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 Bot Management | Security |
| 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 Bot Management | Security |
| 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.