Vulnerability Scan Result


Title: | The Long Hallway |
Description: | The Long Hallway is a thriller anthology series, releasing every Tuesday and Thursday. Behind each door lurks a tale designed to send a chill down your spine. These bite-sized, flash-fiction stories are written by members of the Skylark Media team. Directed by Will Rogers |
ip_address | 204.16.247.189 |
country | US ![]() |
network_name | Teraswitch Networks Inc |
asn | AS20326 |
ip_address | 204.16.247.190 |
country | US ![]() |
network_name | Teraswitch Networks Inc |
asn | AS20326 |
80/tcp | http | Apache - |
443/tcp | https | - - |
Software / Version | Category |
---|---|
Facebook Login | Authentication |
Embedly | Widgets |
Font Awesome 4.7.0 | Font scripts |
Bootstrap 3.3.7 | UI frameworks |
Google Analytics UA | Analytics |
Google Font API | Font scripts |
Apache HTTP Server | Web servers |
jQuery 2.1.1 | JavaScript libraries |
Open Graph | Miscellaneous |
Sectigo | SSL/TLS certificate authorities |
Google Tag Manager | Tag managers |
HSTS | Security |
RSS | Miscellaneous |
Varnish 6.0 | Caching |
Web Application Vulnerabilities
Evidence
Risk Level | CVSS | CVE | Summary | Affected software |
---|---|---|---|---|
6.4 | CVE-2024-6484 | A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser. | bootstrap 3.3.7 | |
4.3 | CVE-2020-11023 | 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. | jquery 2.1.1 | |
4.3 | CVE-2020-11022 | 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. | jquery 2.1.1 | |
4.3 | CVE-2019-11358 | 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. | jquery 2.1.1 | |
4.3 | CVE-2018-20676 | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. | bootstrap 3.3.7 | |
4.3 | CVE-2018-14042 | In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. | bootstrap 3.3.7 | |
4.3 | CVE-2018-14040 | In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. | bootstrap 3.3.7 | |
4.3 | CVE-2016-10735 | In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041. | bootstrap 3.3.7 | |
4.3 | CVE-2015-9251 | 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. | jquery 2.1.1 |
Vulnerability description
We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.
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-1026 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
Vulnerability description
We have noticed that the target application has overly permissive settings in its client access policy files. The crossdomain.xml
file controls the access of externally hosted Flash scripts to this website, while clientaccesspolicy.xml
specifies other sites that can read content from this website - which is normally denied by the Same Origin Policy. This vulnerability arises from configurations that grant excessive permissions to clients.
Risk description
In `crossdomain.xml`, the external websites which are permitted to read content from this website via Flash are specified in the XML tag `<allow-access-from>`. If the value of this tag is too permissive (ex. wildcard), it means that any Flash script from an external website could access content from this website, including confidential information of users. If the allowed domains are too permissive (ex. wildcard) in `clientaccesspolicy.xml`, then any external website will be able to read content (including sensitive information) from this website. Flash is not supported anymore and this poses a risk only if the user's clients use older browsers, making them vulnerable to their information being accessed by a malicious external Flash script.
Recommendation
We recommend to carefully review the content of the policy file and permit access only for legitimate domains.
Classification
CWE | CWE-16 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Evidence
URL | Evidence |
---|---|
https://thelonghallway.libsyn.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
URL | Method | Parameters | Evidence |
---|---|---|---|
https://thelonghallway.libsyn.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 |
|
https://thelonghallway.libsyn.com/12-neurosanguine-blues | 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 |
|
https://thelonghallway.libsyn.com/2019/07 | 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 |
|
https://thelonghallway.libsyn.com/9-this-is-my-cue-to-demateralize | 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 |
|
https://thelonghallway.libsyn.com/happy-halloween | 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
Software / Version | Category |
---|---|
Facebook Login | Authentication |
Embedly | Widgets |
Font Awesome 4.7.0 | Font scripts |
Bootstrap 3.3.7 | UI frameworks |
Google Analytics UA | Analytics |
Google Font API | Font scripts |
Apache HTTP Server | Web servers |
jQuery 2.1.1 | JavaScript libraries |
Open Graph | Miscellaneous |
Sectigo | SSL/TLS certificate authorities |
Google Tag Manager | Tag managers |
HSTS | Security |
RSS | Miscellaneous |
Varnish 6.0 | Caching |
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 | Evidence |
---|---|
https://thelonghallway.libsyn.com/ |
|
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.
Evidence
Vulnerability description
Website is accessible.
Evidence
URL | Method | Parameters | Evidence |
---|---|---|---|
https://thelonghallway.libsyn.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 | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
CWE | CWE-200 |
OWASP Top 10 - 2017 | |
OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
Software / Version | Category |
---|---|
Bootstrap | UI frameworks |
Varnish 6.0 | Caching |
Apache HTTP Server | Web servers |
jQuery | JavaScript libraries |
Google Analytics UA | Analytics |
Embedly | Widgets |
Sectigo | SSL/TLS certificate authorities |
HSTS | Security |
Google Font API | Font scripts |
Font Awesome 4.7.0 | Font scripts |
RSS | Miscellaneous |
Open Graph | 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 |
---|---|---|---|
thelonghallway.libsyn.com | A | IPv4 address | 204.16.247.189 |
thelonghallway.libsyn.com | A | IPv4 address | 204.16.247.190 |
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 |
---|---|
Linux 2.6.32 | 94% |
Vulnerability description
OS Detection