Vulnerability Scan Result
| Title: | Billy King & The Bad Bad Bad |
| Description: | Home page of Billy King & The Bad Bad Bad, a rock group from Austin |
| ip_address | 172.65.197.38 |
| country | - |
| network_name | Cloudflare Inc |
| asn | AS13335 |
7/tcp | tcpwrapped | - - |
9/tcp | tcpwrapped | - - |
13/tcp | tcpwrapped | - - |
20/tcp | tcpwrapped | - - |
21/tcp | tcpwrapped | - - |
22/tcp | tcpwrapped | - - |
23/tcp | tcpwrapped | - - |
25/tcp | tcpwrapped | - - |
26/tcp | tcpwrapped | - - |
37/tcp | tcpwrapped | - - |
42/tcp | tcpwrapped | - - |
43/tcp | tcpwrapped | - - |
53/tcp | tcpwrapped | - - |
70/tcp | tcpwrapped | - - |
79/tcp | tcpwrapped | - - |
80/tcp | http | OpenResty web app server - |
81/tcp | tcpwrapped | - - |
88/tcp | tcpwrapped | - - |
102/tcp | tcpwrapped | - - |
106/tcp | tcpwrapped | - - |
110/tcp | tcpwrapped | - - |
111/tcp | tcpwrapped | - - |
113/tcp | tcpwrapped | - - |
119/tcp | tcpwrapped | - - |
135/tcp | tcpwrapped | - - |
137/tcp | tcpwrapped | - - |
138/tcp | tcpwrapped | - - |
139/tcp | tcpwrapped | - - |
143/tcp | tcpwrapped | - - |
144/tcp | tcpwrapped | - - |
179/tcp | tcpwrapped | - - |
199/tcp | tcpwrapped | - - |
201/tcp | tcpwrapped | - - |
264/tcp | tcpwrapped | - - |
318/tcp | tcpwrapped | - - |
383/tcp | tcpwrapped | - - |
389/tcp | tcpwrapped | - - |
411/tcp | tcpwrapped | - - |
412/tcp | tcpwrapped | - - |
427/tcp | tcpwrapped | - - |
443/tcp | https | OpenResty web app server - |
444/tcp | tcpwrapped | - - |
445/tcp | tcpwrapped | - - |
464/tcp | tcpwrapped | - - |
465/tcp | tcpwrapped | - - |
497/tcp | tcpwrapped | - - |
512/tcp | tcpwrapped | - - |
513/tcp | tcpwrapped | - - |
514/tcp | tcpwrapped | - - |
515/tcp | tcpwrapped | - - |
540/tcp | tcpwrapped | - - |
543/tcp | tcpwrapped | - - |
544/tcp | tcpwrapped | - - |
546/tcp | tcpwrapped | - - |
547/tcp | tcpwrapped | - - |
548/tcp | tcpwrapped | - - |
554/tcp | tcpwrapped | - - |
563/tcp | tcpwrapped | - - |
587/tcp | tcpwrapped | - - |
591/tcp | tcpwrapped | - - |
593/tcp | tcpwrapped | - - |
596/tcp | tcpwrapped | - - |
631/tcp | tcpwrapped | - - |
639/tcp | tcpwrapped | - - |
646/tcp | tcpwrapped | - - |
691/tcp | tcpwrapped | - - |
860/tcp | tcpwrapped | - - |
873/tcp | tcpwrapped | - - |
902/tcp | tcpwrapped | - - |
989/tcp | tcpwrapped | - - |
990/tcp | tcpwrapped | - - |
993/tcp | tcpwrapped | - - |
995/tcp | tcpwrapped | - - |
1025/tcp | tcpwrapped | - - |
1026/tcp | tcpwrapped | - - |
1027/tcp | tcpwrapped | - - |
1028/tcp | tcpwrapped | - - |
1029/tcp | tcpwrapped | - - |
1080/tcp | tcpwrapped | - - |
1110/tcp | tcpwrapped | - - |
1194/tcp | tcpwrapped | - - |
1214/tcp | tcpwrapped | - - |
1241/tcp | tcpwrapped | - - |
1311/tcp | tcpwrapped | - - |
1337/tcp | tcpwrapped | - - |
1433/tcp | tcpwrapped | - - |
1589/tcp | tcpwrapped | - - |
1701/tcp | tcpwrapped | - - |
1720/tcp | tcpwrapped | - - |
1723/tcp | tcpwrapped | - - |
1741/tcp | tcpwrapped | - - |
1755/tcp | tcpwrapped | - - |
1900/tcp | tcpwrapped | - - |
2000/tcp | tcpwrapped | - - |
2001/tcp | tcpwrapped | - - |
2002/tcp | tcpwrapped | - - |
2049/tcp | tcpwrapped | - - |
2078/tcp | tcpwrapped | - - |
2080/tcp | tcpwrapped | - - |
2082/tcp | tcpwrapped | - - |
2083/tcp | tcpwrapped | - - |
2086/tcp | tcpwrapped | - - |
2087/tcp | tcpwrapped | - - |
2100/tcp | tcpwrapped | - - |
2121/tcp | tcpwrapped | - - |
2222/tcp | tcpwrapped | - - |
2483/tcp | tcpwrapped | - - |
2484/tcp | tcpwrapped | - - |
2717/tcp | tcpwrapped | - - |
2967/tcp | tcpwrapped | - - |
3000/tcp | tcpwrapped | - - |
3050/tcp | tcpwrapped | - - |
3128/tcp | tcpwrapped | - - |
3222/tcp | tcpwrapped | - - |
3306/tcp | tcpwrapped | - - |
3389/tcp | tcpwrapped | - - |
3690/tcp | tcpwrapped | - - |
3784/tcp | tcpwrapped | - - |
3986/tcp | tcpwrapped | - - |
4280/tcp | tcpwrapped | - - |
4333/tcp | tcpwrapped | - - |
4444/tcp | tcpwrapped | - - |
4445/tcp | tcpwrapped | - - |
4899/tcp | tcpwrapped | - - |
5000/tcp | tcpwrapped | - - |
5004/tcp | tcpwrapped | - - |
5005/tcp | tcpwrapped | - - |
5009/tcp | tcpwrapped | - - |
5013/tcp | tcpwrapped | - - |
5051/tcp | tcpwrapped | - - |
5060/tcp | tcpwrapped | - - |
5101/tcp | tcpwrapped | - - |
5190/tcp | tcpwrapped | - - |
5222/tcp | tcpwrapped | - - |
5223/tcp | tcpwrapped | - - |
5357/tcp | tcpwrapped | - - |
5432/tcp | tcpwrapped | - - |
5631/tcp | tcpwrapped | - - |
5666/tcp | tcpwrapped | - - |
5800/tcp | tcpwrapped | - - |
5900/tcp | tcpwrapped | - - |
5901/tcp | tcpwrapped | - - |
5985/tcp | tcpwrapped | - - |
5986/tcp | tcpwrapped | - - |
6000/tcp | tcpwrapped | - - |
6001/tcp | tcpwrapped | - - |
6129/tcp | tcpwrapped | - - |
6346/tcp | tcpwrapped | - - |
6347/tcp | tcpwrapped | - - |
6379/tcp | tcpwrapped | - - |
6588/tcp | tcpwrapped | - - |
6646/tcp | tcpwrapped | - - |
6665/tcp | tcpwrapped | - - |
6679/tcp | tcpwrapped | - - |
6699/tcp | tcpwrapped | - - |
7000/tcp | tcpwrapped | - - |
7001/tcp | tcpwrapped | - - |
7070/tcp | tcpwrapped | - - |
7199/tcp | tcpwrapped | - - |
8000/tcp | tcpwrapped | - - |
8008/tcp | tcpwrapped | - - |
8009/tcp | tcpwrapped | - - |
8080/tcp | tcpwrapped | - - |
8081/tcp | tcpwrapped | - - |
8200/tcp | tcpwrapped | - - |
8222/tcp | tcpwrapped | - - |
8443/tcp | tcpwrapped | - - |
8500/tcp | tcpwrapped | - - |
8888/tcp | tcpwrapped | - - |
9000/tcp | tcpwrapped | - - |
9042/tcp | tcpwrapped | - - |
9100/tcp | jetdirect | - - |
9800/tcp | tcpwrapped | - - |
9999/tcp | tcpwrapped | - - |
10000/tcp | tcpwrapped | - - |
10161/tcp | tcpwrapped | - - |
10162/tcp | tcpwrapped | - - |
19638/tcp | tcpwrapped | - - |
20000/tcp | tcpwrapped | - - |
27017/tcp | tcpwrapped | - - |
32768/tcp | tcpwrapped | - - |
49152/tcp | tcpwrapped | - - |
49153/tcp | tcpwrapped | - - |
49154/tcp | tcpwrapped | - - |
49155/tcp | tcpwrapped | - - |
49156/tcp | tcpwrapped | - - |
49157/tcp | tcpwrapped | - - |
| Software / Version | Category |
|---|---|
| jQuery-pjax | Mobile frameworks |
| jQuery Migrate | JavaScript libraries |
| Isotope | JavaScript libraries |
| jQuery 1.12.4 | JavaScript libraries |
| lit-element 3.2.1 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| OpenResty | Web servers |
| Skrollr 0.6.29 | JavaScript libraries |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Stimulus | JavaScript frameworks |
| Turbo | Performance |
| reCAPTCHA | Security |
| HSTS | Security |
| SoundManager \1 | JavaScript libraries |
| Varnish | Caching |
| YouTube | Video players |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.21319 | 0.9541 | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-11022 | 6.9 | 0.22547 | 0.95559 | In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2019-11358 | 6.1 | 0.02403 | 0.84446 | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
| CVE-2015-9251 | 6.1 | 0.12796 | 0.93664 | jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.billykingandthebadbadbad.com/ | 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
| Software / Version | Category |
|---|---|
| jQuery-pjax | Mobile frameworks |
| jQuery Migrate | JavaScript libraries |
| Isotope | JavaScript libraries |
| jQuery 1.12.4 | JavaScript libraries |
| lit-element 3.2.1 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| OpenResty | Web servers |
| Skrollr 0.6.29 | JavaScript libraries |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Stimulus | JavaScript frameworks |
| Turbo | Performance |
| reCAPTCHA | Security |
| HSTS | Security |
| SoundManager \1 | JavaScript libraries |
| Varnish | Caching |
| YouTube | Video players |
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 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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.billykingandthebadbadbad.com/ | GET | 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 |
|
Vulnerability description
We noticed that the target application is serving mixed content. This occurs when initial HTML is loaded over a secure HTTPS connection, but other resources (such as images, videos, stylesheets, scripts) are loaded over an insecure HTTP connection. This is called mixed content because both HTTP and HTTPS content are being loaded to display the same page, and the initial request was secure over HTTPS.
Risk description
The risk is that the insecurely loaded resources (HTTP) on an otherwise secure page (HTTPS) can be intercepted or manipulated by attackers, potentially leading to eavesdropping or content tampering.
Recommendation
Ensure that all external resources the page references are loaded using HTTPS.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.billykingandthebadbadbad.com/ | GET | 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 | Suspicious comment bug found in: |
Vulnerability description
We have discovered that the target application's code contains suspicious comments that may be related to potential bugs, incomplete functionality, or weaknesses. These comments often arise during development and testing phases but are inadvertently left in the code.
Risk description
The risk exists that attackers could analyze these comments to identify vulnerabilities or weaknesses in the application. While comments themselves do not directly lead to security breaches, they may guide attackers to focus their efforts on specific parts of the application, potentially uncovering and exploiting vulnerabilities.
Recommendation
Remove comments that suggest the presence of bugs, incomplete functionality, or weaknesses, before deploying the application.
Classification
| CWE | CWE-209 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
Vulnerability description
Website is accessible.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.billykingandthebadbadbad.com/ | GET | 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 | Email Address: spaceflightrecords@gmail.com billyking@thebadbadbad.com |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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: dns4.sitezoogle.com, dns2.sitezoogle.com, dns1.sitezoogle.com, dns3.sitezoogle.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 |
|---|---|---|---|
| www.billykingandthebadbadbad.com | SPF | Sender Policy Framework | "v=spf1 a mx include:emailsrvr.com include:sendgrid.net include:sendgrid.bandzoogle.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
| Software / Version | Category |
|---|---|
| Ruby | Programming languages |
| YouTube | Video players |
| Ruby on Rails | Web frameworks |
| Varnish | Caching |
| Nginx | Web servers, Reverse proxies |
| Stimulus | JavaScript frameworks |
| jQuery-pjax | Mobile frameworks |
| OpenResty | Web servers |
| jQuery | JavaScript libraries |
| reCAPTCHA | Security |
| HSTS | 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.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.billykingandthebadbadbad.com | A | IPv4 address | 172.65.197.38 |
| www.billykingandthebadbadbad.com | NS | Name server | dns4.sitezoogle.com |
| www.billykingandthebadbadbad.com | NS | Name server | dns2.sitezoogle.com |
| www.billykingandthebadbadbad.com | NS | Name server | dns1.sitezoogle.com |
| www.billykingandthebadbadbad.com | NS | Name server | dns3.sitezoogle.com |
| www.billykingandthebadbadbad.com | MX | Mail server | 10 mx1.emailsrvr.com |
| www.billykingandthebadbadbad.com | MX | Mail server | 20 mx2.emailsrvr.com |
| www.billykingandthebadbadbad.com | SOA | Start of Authority | dns1.sitezoogle.com. info.sitezoogle.com. 2023042702 86400 7200 3600000 172800 |
| www.billykingandthebadbadbad.com | AAAA | IPv6 address | 2606:4700:90:0:3626:d0ff:6957:de1 |
| www.billykingandthebadbadbad.com | SPF | Sender Policy Framework | "v=spf1 a mx include:emailsrvr.com include:sendgrid.net include:sendgrid.bandzoogle.com ~all" |
| www.billykingandthebadbadbad.com | CNAME | Canonical name | billykingandthebadbadbad.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
| Operating System | Accuracy |
|---|---|
| FreeBSD 11.0-RELEASE | 89% |
Vulnerability description
OS Detection