Vulnerability Scan Result
| Title: | (PDF) Сокирко О. Іван Мазепа як ранньомодерний володар //Український історичний журнал. - 2024. - Число 5. - С. 40-61 |
| Description: | Th e purpose of the article is to analyze the fi gure of Hetman Ivan Mazepa and his activities in the context of institutional, social, and worldview changes experienced by the states of Early Modern Europe. Retrospective analysis of the numerous |
| ip_address | 13.32.27.63 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 13.32.27.124 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 13.32.27.104 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 13.32.27.127 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | CloudFront - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Apple Sign-in | Authentication |
| Facebook Login | Authentication |
| Google Sign-in | Authentication |
| Font Awesome | Font scripts |
| core-js 2.6.12 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 1.8.3 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Select2 | JavaScript libraries |
| Sentry | Issue trackers |
| Google Tag Manager | Tag managers |
| Lodash 4.17.19 | JavaScript libraries |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 6.5 | CVE-2021-23337 | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. | lodash 4.17.19 | |
| 5.8 | CVE-2020-8203 | Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. | lodash 4.17.19 | |
| 5 | CVE-2020-28500 | Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. | lodash 4.17.19 | |
| 4.3 | CVE-2012-6708 | jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common. | jquery 1.8.3 | |
| 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 1.8.3 | |
| 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 1.8.3 | |
| 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 1.8.3 | |
| 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 1.8.3 |
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
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.academia.edu/125049014/Сокирко_О_Іван_Мазепа_як_ранньомодерний_володар_Український_історичний_журнал_2024_Число_5_С_40_61 | auvid | Set-Cookie: .academia.edu |
Vulnerability description
We found that the target application sets cookies with a domain scope that is too broad. Specifically, cookies intended for use within a particular application are configured in such a way that they can be accessed by multiple subdomains of the same primary domain.
Risk description
The risk is that a cookie set for example.com may be sent along with the requests sent to dev.example.com, calendar.example.com, hostedsite.example.com. Potentially risky websites under your main domain may access those cookies and use the victim session from the main site.
Recommendation
The `Domain` attribute should be set to the origin host to limit the scope to that particular server. For example if the application resides on server app.mysite.com, then it should be set to `Domain=app.mysite.com`
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.academia.edu/125049014/Сокирко_О_Іван_Мазепа_як_ранньомодерний_володар_Український_історичний_журнал_2024_Число_5_С_40_61 | request_id, overridden_user_tests, auvid, ab_tests, has_seen_cookie_banner | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: request_id=h_DM_PT4h57QB5RLqFEhsbDy6PWqeQSe9wTPU1w2JEtjtc16RghUjA%3D%3D Set-Cookie: overridden_user_tests=%7B%7D Set-Cookie: auvid=MTc0OTg4OTI4NTIzODowLjI0ODE5Nzk0NTUwMDU5ODY%3D Set-Cookie: ab_tests=%7B%22full_page_mobile_sutd_modal%22%3A%22control%22%7D Set-Cookie: has_seen_cookie_banner=true |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.academia.edu/125049014/Сокирко_О_Іван_Мазепа_як_ранньомодерний_володар_Український_історичний_журнал_2024_Число_5_С_40_61 | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon CloudFront | CDN |
| Apple Sign-in | Authentication |
| Facebook Login | Authentication |
| Google Sign-in | Authentication |
| Font Awesome | Font scripts |
| core-js 2.6.12 | JavaScript libraries |
| Google Analytics GA4 | Analytics |
| jQuery 1.8.3 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| React | JavaScript frameworks |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| Select2 | JavaScript libraries |
| Sentry | Issue trackers |
| Google Tag Manager | Tag managers |
| Lodash 4.17.19 | JavaScript libraries |
| 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
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.
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
| CVE | CVSS | EPSS Score | EPSS Percentile | CISA KEV | Summary |
|---|---|---|---|---|---|
| CVE-2024-6484 | 6.4 | 0.00044 | 0.13184 | 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. |
| CVE-2018-14040 | 4.3 | 0.01633 | 0.81043 | No | In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. |
| CVE-2018-14042 | 4.3 | 0.017 | 0.81432 | No | In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. |
| CVE-2016-10735 | 4.3 | 0.06152 | 0.90331 | No | 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. |
| CVE-2018-20676 | 4.3 | 0.05526 | 0.89743 | No | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. |
Vulnerability description
Vulnerabilities found for Bootstrap 3.3.2
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
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.academia.edu | A | IPv4 address | 13.32.27.124 |
| www.academia.edu | A | IPv4 address | 13.32.27.104 |
| www.academia.edu | A | IPv4 address | 13.32.27.63 |
| www.academia.edu | A | IPv4 address | 13.32.27.127 |
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
Vulnerability description
OS detection couldn't determine the operating system.
Evidence
We managed to detect the redirect using the following Request / Response chain.
Recommendation
Vulnerability checks are skipped for ports that redirect to another port. We recommend scanning the redirected port directly.
Evidence
| Software / Version | Category |
|---|---|
| Bootstrap 3.3.2 | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| Amazon Web Services | PaaS |
| Google Analytics GA4 | Analytics |
| reCAPTCHA | Security |
| HSTS | Security |
| Amazon S3 | CDN |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
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.