Vulnerability Scan Result
| Title: | HedgeDoc - Collaborative markdown notes |
| Description: | No description found |
| ip_address | 131.246.168.147 |
| country | DE  |
| network_name | Technische Universitaet Kaiserslautern |
| asn | AS199578 |
80/tcp | http | nginx - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Babel | Miscellaneous |
| Express | Web frameworks, Web servers |
| Bootstrap 3.4.1 | UI frameworks |
| core-js 2.6.12 | JavaScript libraries |
| jQuery 3.7.0 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Moment.js 2.29.4 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Node.js | Programming languages |
| Open Graph | Miscellaneous |
| Prism | Miscellaneous |
| Socket.io | JavaScript frameworks |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Lodash 4.17.21 | JavaScript libraries |
| MathJax 2.7.9 | JavaScript graphics |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2023-39663 | 7.5 | 0.00211 | 0.43731 | Mathjax up to v2.7.9 was discovered to contain two Regular expression Denial of Service (ReDoS) vulnerabilities in MathJax.js via the components pattern and markdownPattern. NOTE: the vendor disputes this because the regular expressions are not applied to user input; thus, there is no risk. |
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-6484 | 6.4 | 0.00049 | 0.15167 | 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. |
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://hedge.fachschaft.informatik.uni-kl.de/ikNyVJocRV-Z5YSjVaC6fA/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Babel | Miscellaneous |
| Express | Web frameworks, Web servers |
| Bootstrap 3.4.1 | UI frameworks |
| core-js 2.6.12 | JavaScript libraries |
| jQuery 3.7.0 | JavaScript libraries |
| jQuery UI 1.13.2 | JavaScript libraries |
| Moment.js 2.29.4 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Node.js | Programming languages |
| Open Graph | Miscellaneous |
| Prism | Miscellaneous |
| Socket.io | JavaScript frameworks |
| PWA | Miscellaneous |
| Webpack | Miscellaneous |
| Lodash 4.17.21 | JavaScript libraries |
| MathJax 2.7.9 | JavaScript graphics |
| 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
| URL | Evidence |
|---|---|
| https://hedge.fachschaft.informatik.uni-kl.de/ikNyVJocRV-Z5YSjVaC6fA/ | 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 |
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.
Evidence
Vulnerability description
Website is accessible.
Evidence
| URL | Method | Summary |
|---|---|---|
| https://hedge.fachschaft.informatik.uni-kl.de/ikNyVJocRV-Z5YSjVaC6fA/ | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET,HEAD` Request / Response |
Vulnerability description
We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.
Risk description
The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.
Recommendation
We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.
Classification
| CWE | CWE-16 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| hedge.fachschaft.informatik.uni-kl.de | A | IPv4 address | 131.246.168.147 |
| hedge.fachschaft.informatik.uni-kl.de | MX | Mail server | 5 mailgate2.uni-kl.de |
| hedge.fachschaft.informatik.uni-kl.de | MX | Mail server | 10 mailgate1.uni-kl.de |
| hedge.fachschaft.informatik.uni-kl.de | AAAA | IPv6 address | 2001:638:208:4801:5054:ff:feb3:2beb |
| hedge.fachschaft.informatik.uni-kl.de | CNAME | Canonical name | murray.fachschaft.informatik.uni-kl.de |
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
| Software / Version | Category |
|---|---|
| Node.js | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Express | Web frameworks, Web servers |
| HSTS | Security |
| PWA | 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
| Operating System | Accuracy |
|---|---|
| Linux 4.15 - 5.6 | 100% |
Vulnerability description
OS Detection