Vulnerability Scan Result
| Title: | BLOCKALARM® | Alarmanlage & Sicherheitstechnik München |
| Description: | Funkalarmanlage aus München für Haus + Firma ✓ TESTSIEGER 2023 ✓ zertifiziert 50131.1 Grad 2 ✓ kostenfreie Beratung ✓ Blockalarm® |
| IP address | 185.30.35.36 |
| Country | DE  |
| AS number | AS48324 |
| Net name | Webgo GMBH |
No open ports were found.
| Software / Version | Category |
|---|---|
| Buttonizer | Widgets |
| GeneratePress GP Premium 2.5.2 | WordPress plugins |
| GeneratePress 3.5.1 | WordPress themes |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Ivory Search 5.5.11 | WordPress plugins |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Select2 | JavaScript libraries |
| Underscore.js 1.13.4 | JavaScript libraries |
| WordPress | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| reCAPTCHA | Security |
| Max Mega Menu 3.5 | Widgets, WordPress plugins |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.blockalarm.de/ | 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 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
| Software / Version | Category |
|---|---|
| Buttonizer | Widgets |
| GeneratePress GP Premium 2.5.2 | WordPress plugins |
| GeneratePress 3.5.1 | WordPress themes |
| jQuery Migrate 3.4.1 | JavaScript libraries |
| Ivory Search 5.5.11 | WordPress plugins |
| jQuery | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| RankMath SEO | WordPress plugins, SEO |
| Select2 | JavaScript libraries |
| Underscore.js 1.13.4 | JavaScript libraries |
| WordPress | CMS, Blogs |
| WP Rocket | Caching, WordPress plugins |
| reCAPTCHA | Security |
| Max Mega Menu 3.5 | Widgets, WordPress plugins |
| 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.
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
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).
Classification
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Evidence
Vulnerability description
Website is accessible.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.blockalarm.de/ | 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 | Email Address: dpo-google@google.com info@blockalarm.de msft@microsoft.com |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | A6: Security Misconfiguration |
| OWASP Top 10 - 2021 | A4: Insecure Design |
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
| OWASP Top 10 - 2017 | A6 - Security Misconfiguration |
| OWASP Top 10 - 2021 | A5 - Security Misconfiguration |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| blockalarm.de | A | IPv4 address | 185.30.35.36 |
| blockalarm.de | NS | Name server | ns6.kasserver.com |
| blockalarm.de | NS | Name server | ns5.kasserver.com |
| blockalarm.de | MX | Mail server | 10 w0134553.kasserver.com |
| blockalarm.de | SOA | Start of Authority | ns5.kasserver.com. hostmaster.kasserver.com. 2502231013 28800 7200 1209600 7200 |
| blockalarm.de | TXT | Text record | "google-site-verification=GPkrBvzhL5e77AiFpgLUpUZYn07QJlozObefRRdTFfM" |
| blockalarm.de | SPF | Sender Policy Framework | "v=spf1 mx a ?all" |
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.