Vulnerability Scan Result
| Title: | CZ-Nachweismeldung |
| Description: | No description found |
| ip_address | 176.9.86.112 |
| country | DE  |
| network_name | Hetzner Online GmbH |
| asn | AS24940 |
80/tcp | http | Microsoft IIS httpd 10 |
135/tcp | msrpc | Microsoft Windows RPC - |
139/tcp | netbios-ssn | Microsoft Windows netbios-ssn - |
443/tcp | https | - - |
445/tcp | microsoft-ds | - - |
| Software / Version | Category |
|---|---|
| Angular 15.1.5 | JavaScript frameworks |
| Zone.js | JavaScript frameworks |
| core-js 3.6.5 | JavaScript libraries |
| Marko | Web frameworks, UI frameworks |
| Windows Server | Operating systems |
| Node.js | Programming languages |
| Microsoft ASP.NET | Web frameworks |
| IIS 10.0 | Web servers |
| HSTS | Security |
| TypeScript | Programming languages |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2026-41423 | 8.7 | 0.00246 | 0.15662 | Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8, a Server-Side Request Forgery (SSRF) vulnerability exists in @angular/platform-server due to improper handling of URLs during Server-Side Rendering (SSR). When an attacker sends a request such as GET /\evil.com/ HTTP/1.1 the server engine (Express, etc.) passes the URL string to Angular’s rendering functions. Because the URL parser normalizes the backslash to a forward slash for HTTP/HTTPS schemes, the internal state of the application is hijacked to believe the current origin is evil.com. This misinterpretation tricks the application into treating the attacker’s domain as the local origin. Consequently, any relative HttpClient requests or PlatformLocation.hostname references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services. This issue has been patched in versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8. |
| CVE-2026-22610 | 8.5 | 0.00444 | 0.35155 | Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0, a cross-site scripting (XSS) vulnerability has been identified in the Angular Template Compiler. The vulnerability exists because Angular’s internal sanitization schema fails to recognize the href and xlink:href attributes of SVG <script> elements as a Resource URL context. This issue has been patched in versions 19.2.18, 20.3.16, 21.0.7, and 21.1.0-rc.0. |
| CVE-2025-66412 | 8.5 | 0.00371 | 0.28688 | Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 21.0.2, 20.3.15, and 19.2.17, A Stored Cross-Site Scripting (XSS) vulnerability has been identified in the Angular Template Compiler. It occurs because the compiler's internal security schema is incomplete, allowing attackers to bypass Angular's built-in security sanitization. Specifically, the schema fails to classify certain URL-holding attributes (e.g., those that could contain javascript: URLs) as requiring strict URL security, enabling the injection of malicious scripts. This vulnerability is fixed in 21.0.2, 20.3.15, and 19.2.17. |
| CVE-2026-27970 | 7.6 | 0.00432 | 0.34323 | Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Versions prior to 21.2.0, 21.1.16, 20.3.17, and 19.2.19 have a cross-Site scripting vulnerability in the Angular internationalization (i18n) pipeline. In ICU messages (International Components for Unicode), HTML from translated content was not properly sanitized and could execute arbitrary JavaScript. Angular i18n typically involves three steps, extracting all messages from an application in the source language, sending the messages to be translated, and then merging their translations back into the final source code. Translations are frequently handled by contracts with specific partner companies, and involve sending the source messages to a separate contractor before receiving final translations for display to the end user. If the returned translations have malicious content, it could be rendered into the application and execute arbitrary JavaScript. When successfully exploited, this vulnerability allows for execution of attacker controlled JavaScript in the application origin. Depending on the nature of the application being exploited this could lead to credential exfiltration and/or page vandalism. Several preconditions apply to the attack. The attacker must compromise the translation file (xliff, xtb, etc.). Unlike most XSS vulnerabilities, this issue is not exploitable by arbitrary users. An attacker must first compromise an application's translation file before they can escalate privileges into the Angular application client. The victim application must use Angular i18n, use one or more ICU messages, render an ICU message, and not defend against XSS via a safe content security policy. Versions 21.2.0, 21.1.6, 20.3.17, and 19.2.19 patch the issue. Until the patch is applied, developers should consider reviewing and verifying translated content received from untrusted third parties before incorporating it in an Angular application, enabling strict CSP controls to block unauthorized JavaScript from executing on the page, and enabling Trusted Types to enforce proper HTML sanitization. |
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://ol-immu.gesundheitsamt-service.de/ | 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 |
Evidence
| Software / Version | Category |
|---|---|
| Angular 15.1.5 | JavaScript frameworks |
| Zone.js | JavaScript frameworks |
| core-js 3.6.5 | JavaScript libraries |
| Marko | Web frameworks, UI frameworks |
| Windows Server | Operating systems |
| Node.js | Programming languages |
| Microsoft ASP.NET | Web frameworks |
| IIS 10.0 | Web servers |
| HSTS | Security |
| TypeScript | Programming languages |
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 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Windows Server Message Blocks (SMB) service. PORT STATE SERVICE VERSION 139/tcp open netbios-ssn Microsoft Windows netbios-ssn
Vulnerability description
We found that the Windows Server Message Blocks (SMB) service is publicly accessible. The Server Message Block (SMB) protocol facilitates services like file and print sharing on systems. Older SMB protocol versions operate through NetBIOS to enable application-layer networking for devices within Windows operating systems, including communication with printers and serial ports.
Risk description
Exposing this service online can enable attackers to launch authentication attacks, like guessing login credentials, potentially gaining unauthorized access. Attackers might use publicly available employee information for brute-force attacks. Vulnerabilities, such as unpatched software or protocol flaws, could also be exploited. An example is MS17-010 (EternalBlue) vulnerability. Additionally, integration with Active Directory Domain Services could allow attackers to move laterally across the network, accessing more systems and sensitive data.
Recommendation
We recommend turning off SMB access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). Avoid permitting direct user authentication to Active Directory over the Internet to prevent attackers from engaging in password guessing or causing the lockout of legitimate domain user accounts. If the SMB service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall.
Evidence
We managed to detect a publicly accessible Remote Procedure Call (RPC) service. PORT STATE SERVICE VERSION 135/tcp open msrpc Microsoft Windows RPC
Vulnerability description
We found that the Windows Remote Procedure Call (RPC) service is publicly accessible. RPC is a protocol that one program can use to request a service from a program located on another computer in a network.
Risk description
Exposing this service online can enable attackers to launch attacks, including unauthorized access, remote code execution, information disclosure, denial of service (DoS), and potential lateral movement within the network.
Recommendation
We recommend turning off RPC access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the RPC service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall.
Evidence
| Operating System | Accuracy |
|---|---|
| Microsoft Windows XP SP3 | 85% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| ol-immu.gesundheitsamt-service.de | A | IPv4 address | 176.9.86.112 |
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 |
| Windows Server | Operating systems |
| Marko | Web frameworks, UI frameworks |
| Microsoft ASP.NET | Web frameworks |
| IIS 10.0 | Web servers |
| 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.