Vulnerability Scan Result
| Title: | Cruises: Norwegian Cruise Line Holiday Deals | NCL |
| Description: | Cruises to Alaska, Hawaii, Bahamas, Europe, or Caribbean. Weekend getaways and great cruise specials. Experience Free at Sea™ with Norwegian Cruise Line. |
| ip_address | 104.102.19.17 |
| country | DE  |
| network_name | Akamai Technologies, Inc. |
| asn | AS16625 |
80/tcp | http | AkamaiGHost - |
443/tcp | https | AkamaiGHost - |
| Software / Version | Category |
|---|---|
| AccessiBe | Accessibility |
| Akamai | CDN |
| Boomerang | JavaScript libraries, RUM |
| AngularJS 1.8.3 | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Babel | Miscellaneous |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Akamai mPulse | RUM |
| Raphael 2.2.0 | JavaScript graphics |
| Adobe Experience Platform Identity Service | Customer data platform |
| Adobe Experience Platform Launch | Tag managers |
| Bootstrap 4.1.3 | UI frameworks |
| jQuery Migrate 1.4.0 | JavaScript libraries |
| core-js 2.6.12 | JavaScript libraries |
| HeadJS | JavaScript libraries, Performance |
| jQuery 3.5.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| New Relic | RUM |
| Nginx | Web servers, Reverse proxies |
| PayPal | Payment processors |
| PHP | Programming languages |
| Popper | Miscellaneous |
| Select2 | JavaScript libraries |
| Webpack | Miscellaneous |
| Adobe Analytics | Analytics |
| Akamai Bot Manager | Security |
| DigiCert | SSL/TLS certificate authorities |
| Drupal | CMS |
| Envoy | Reverse proxies |
| Lodash 1.9.1 | JavaScript libraries |
| MyFonts | Font scripts |
| OneTrust | Cookie compliance |
| Play | Web frameworks |
| HSTS | Security |
| Rokt | Personalisation |
| Scala | Programming languages |
| ServiceNow | Miscellaneous |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2023-26118 | 5.3 | 0.01695 | 0.74152 | Versions of the package angular from 1.4.9 are vulnerable to Regular Expression Denial of Service (ReDoS) via the <input type="url"> element due to the usage of an insecure regular expression in the input[url] functionality. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. |
| CVE-2023-26117 | 5.3 | 0.01695 | 0.74152 | Versions of the package angular from 1.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the $resource service due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. |
| CVE-2023-26116 | 5.3 | 0.01695 | 0.74152 | Versions of the package angular from 1.2.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the angular.copy() utility function due to the usage of an insecure regular expression. Exploiting this vulnerability is possible by a large carefully-crafted input, which can result in catastrophic backtracking. |
| CVE-2022-25844 | 5.3 | 0.04368 | 0.90011 | The package angular after 1.7.0 are vulnerable to Regular Expression Denial of Service (ReDoS) by providing a custom locale rule that makes it possible to assign the parameter in posPre: ' '.repeat() of NUMBER_FORMATS.PATTERNS[1].posPre with a very high value. **Note:** 1) This package has been deprecated and is no longer maintained. 2) The vulnerable versions are 1.7.0 and higher. |
| CVE-2024-8373 | 4.8 | 0.00599 | 0.43989 | Improper sanitization of the value of the [srcset] attribute in <source> HTML elements in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing . This issue affects all versions of AngularJS. Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status . |
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
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2024-6531 | 6.4 | 0.00072 | 0.22588 | 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. |
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
| Software / Version | Category |
|---|---|
| AccessiBe | Accessibility |
| Akamai | CDN |
| Boomerang | JavaScript libraries, RUM |
| AngularJS 1.8.3 | JavaScript frameworks |
| Amazon Web Services | PaaS |
| Amazon S3 | CDN |
| Babel | Miscellaneous |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Akamai mPulse | RUM |
| Raphael 2.2.0 | JavaScript graphics |
| Adobe Experience Platform Identity Service | Customer data platform |
| Adobe Experience Platform Launch | Tag managers |
| Bootstrap 4.1.3 | UI frameworks |
| jQuery Migrate 1.4.0 | JavaScript libraries |
| core-js 2.6.12 | JavaScript libraries |
| HeadJS | JavaScript libraries, Performance |
| jQuery 3.5.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| New Relic | RUM |
| Nginx | Web servers, Reverse proxies |
| PayPal | Payment processors |
| PHP | Programming languages |
| Popper | Miscellaneous |
| Select2 | JavaScript libraries |
| Webpack | Miscellaneous |
| Adobe Analytics | Analytics |
| Akamai Bot Manager | Security |
| DigiCert | SSL/TLS certificate authorities |
| Drupal | CMS |
| Envoy | Reverse proxies |
| Lodash 1.9.1 | JavaScript libraries |
| MyFonts | Font scripts |
| OneTrust | Cookie compliance |
| Play | Web frameworks |
| HSTS | Security |
| Rokt | Personalisation |
| Scala | Programming languages |
| ServiceNow | 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.
Classification
| CWE | CWE-200 |
| 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
| URL | Evidence |
|---|---|
| https://www.ncl.com/uk/en/ | 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-1021 |
| 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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2024-6531 | 6.4 | 0.00072 | 0.22588 | No | 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. |
Vulnerability description
Vulnerabilities found for Bootstrap 4.1.3
Risk description
These vulnerabilities expose the affected applications to the risk of unauthorized access to confidential data and possibly to denial of service attacks. An attacker could search for an appropriate exploit (or create one) for any of these vulnerabilities and use it to attack the system. Notes: - The vulnerabilities are identified based on the server's version.; - Only the first 5 vulnerabilities with the highest risk are shown for each port.; 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
We recommend you to upgrade the affected software to the latest version in order to eliminate the risks imposed by these vulnerabilities.
Evidence
We managed to detect that Bootstrap has reached the End-of-Life (EOL).
Version detected: 4.1.3 End-of-life date: 2023-01-01 Latest version for the cycle: 4.6.2 This release cycle (4) does have long-term-support (LTS). The cycle was released on 2018-01-18 and its latest release date was 2022-07-19. The support ended on 2021-11-01.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
We managed to detect that AngularJS has reached the End-of-Life (EOL).
Version detected: 1.8.3 End-of-life date: 2021-12-31 Latest version for the cycle: 1.8.3 This release cycle (1.8) does have long-term-support (LTS). The cycle was released on 2020-06-04 and its latest release date was 2022-04-07.
Risk description
Using end-of-life (EOL) software poses significant security risks for organizations. EOL software no longer receives updates, including critical security patches. This creates a vulnerability landscape where known and potentially new security flaws remain unaddressed, making the software an attractive target for malicious actors. Attackers can exploit these vulnerabilities to gain unauthorized access, disrupt services, or steal sensitive data. Moreover, without updates, compatibility issues arise with newer technologies, leading to operational inefficiencies and increased potential for system failures. Additionally, regulatory and compliance risks accompany the use of EOL software. Many industries have strict data protection regulations that require up-to-date software to ensure the highest security standards. Non-compliance can result in hefty fines and legal consequences. Organizations also risk damaging their reputation if a breach occurs due to outdated software, eroding customer trust and potentially leading to a loss of business. Therefore, continuing to use EOL software undermines both security posture and business integrity, necessitating timely upgrades and proactive risk management strategies.
Recommendation
To mitigate the risks associated with end-of-life (EOL) software, it's crucial to take proactive steps. Start by identifying any EOL software currently in use within your organization. Once identified, prioritize upgrading or replacing these applications with supported versions that receive regular updates and security patches. This not only helps close security gaps but also ensures better compatibility with newer technologies, enhancing overall system efficiency and reliability.Additionally, develop a comprehensive software lifecycle management plan. This plan should include regular audits to identify upcoming EOL dates and a schedule for timely updates or replacements. Train your IT staff and users about the importance of keeping software up to date and the risks associated with using outdated versions. By maintaining a proactive approach to software management, you can significantly reduce security risks, ensure compliance with industry regulations, and protect your organization's reputation and customer trust.
Evidence
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 94% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Drupal | CMS |
| Cart Functionality | Ecommerce |
| PHP | Programming languages |
| Scala | Programming languages |
| Raphael 2.2.0 | JavaScript graphics |
| Vimeo | Video players |
| Bootstrap 4.1.3 | UI frameworks |
| Envoy | Reverse proxies |
| Nginx | Web servers, Reverse proxies |
| Adobe Experience Platform Identity Service | Customer data platform |
| Play | Web frameworks |
| Amazon Web Services | PaaS |
| AngularJS 1.8.3 | JavaScript frameworks |
| PayPal | Payment processors |
| Moment.js 2.29.4 | JavaScript libraries |
| Hammer.js 2.0.7 | JavaScript libraries |
| core-js 2.6.5 | JavaScript libraries |
| OneTrust | Cookie compliance |
| Akamai Bot Manager | Security |
| Select2 | JavaScript libraries |
| New Relic | RUM |
| Lodash 1.9.1 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| jQuery Migrate 1.4.0 | JavaScript libraries |
| jQuery 3.5.1 | JavaScript libraries |
| HeadJS | JavaScript libraries, Performance |
| Boomerang | JavaScript libraries, RUM |
| Adobe Experience Platform Launch | Tag managers |
| Adobe Analytics | Analytics |
| AccessiBe | Accessibility |
| Akamai mPulse | RUM |
| Rokt | Personalisation |
| MyFonts | Font scripts |
| Linkedin Insight Tag | Analytics |
| Linkedin Ads | Advertising |
| HSTS | Security |
| DigiCert | SSL/TLS certificate authorities |
| Amazon S3 | CDN |
| Akamai | CDN |
| Webpack | Miscellaneous |
| Babel | Miscellaneous |
| ServiceNow | Miscellaneous |
| Popper | 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 |
|---|---|---|---|
| www.ncl.com | A | IPv4 address | 104.102.19.17 |
| www.ncl.com | CNAME | Canonical name | www.ncl.com.edgekey.net |
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.