Vulnerability Scan Result
| Title: | Forside | Bruun og Hjejle |
| Description: | Vi er et førende dansk advokatfirma med fokus på komplekse transaktioner og tvister. |
| ip_address | 77.247.71.110 |
| country | DK  |
| network_name | Ripe NCC ASN Block |
| asn | AS31590 |
22/tcp | ssh | OpenSSH 9.6p1 Ubuntu 3ubuntu13.14 |
80/tcp | http | nginx 1.28.0 |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Microsoft Clarity | Analytics |
| Cookie Information | Cookie compliance |
| Google Analytics | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| PWA | Miscellaneous |
| Drupal 10 | CMS |
| Google Tag Manager | Tag managers |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.bruunhjejle.dk/ | 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
| URL | Evidence |
|---|---|
| https://www.bruunhjejle.dk/ | Response headers do not include the HTTP Strict-Transport-Security header |
Vulnerability description
We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.
Risk description
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.bruunhjejle.dk/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Microsoft Clarity | Analytics |
| Cookie Information | Cookie compliance |
| Google Analytics | Analytics |
| jQuery 3.7.1 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| PHP | Programming languages |
| PWA | Miscellaneous |
| Drupal 10 | CMS |
| Google Tag Manager | Tag managers |
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
| URL | Method | Summary |
|---|---|---|
| https://www.bruunhjejle.dk/ | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: GET, POST` 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 |
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
We managed to detect a publicly accessible SSH service. Starting Nmap ( https://nmap.org ) at 2025-12-03 19:37 EET Nmap scan report for www.bruunhjejle.dk (77.247.71.110) Host is up (0.013s latency).
PORT STATE SERVICE VERSION 22/tcp open ssh OpenSSH 9.6p1 Ubuntu 3ubuntu13.14 (Ubuntu Linux; protocol 2.0) | ssh-auth-methods: | Supported authentication methods: | publickey |_ password Service Info: OS: Linux; CPE: cpe:/o:linux:linux_kernel
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 1.17 seconds
Vulnerability description
We found that the SSH service with username/password authentication is publicly accessible. Network administrators often use remote administration protocols to control devices like switches, routers, and other essential systems. However, allowing these services to be accessible via the Internet can increase security risks, creating potential opportunities for attacks on the organization.
Risk description
Exposing this service online with username/password authentication can enable attackers to launch authentication attacks, like guessing login credentials, and potentially gaining unauthorized access. Vulnerabilities, such as unpatched software, protocol flaws, or backdoors could also be exploited. An example is the CVE-2024-3094 (XZ Utils Backdoor) vulnerability.
Recommendation
We recommend turning off SSH with username/password authentication access over the Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the SSH service is essential for business purposes, we recommend limiting access only from designated IP addresses using a firewall. Furthermore, it is advisable to utilize SSH Public Key Authentication since it employs a key pair to verify the identity of a user or process.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns01.one.com, ns02.one.com
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.bruunhjejle.dk | A | IPv4 address | 77.247.71.110 |
| www.bruunhjejle.dk | NS | Name server | ns01.one.com |
| www.bruunhjejle.dk | NS | Name server | ns02.one.com |
| www.bruunhjejle.dk | MX | Mail server | 1 mx1-dk.centerasecurity.dk |
| www.bruunhjejle.dk | MX | Mail server | 1 mx2-dk.centerasecurity.dk |
| www.bruunhjejle.dk | MX | Mail server | 2 mx3-dk.centerasecurity.dk |
| www.bruunhjejle.dk | SOA | Start of Authority | ns01.one.com. hostmaster.one.com. 2025111201 14400 3600 1209600 600 |
| www.bruunhjejle.dk | TXT | Text record | "MS=ms70048667" |
| www.bruunhjejle.dk | TXT | Text record | "M1+7WGLPXBYEBLVQV6Xafgk8Gt8PDaT4kx/w8SBv8Sc=" |
| www.bruunhjejle.dk | TXT | Text record | "docusign=5585aa36-4d30-4110-af5a-bbc6eb3abe1c" |
| www.bruunhjejle.dk | TXT | Text record | "docusign=8b8fdde1-e490-4523-bb31-bfc11c5f8002" |
| www.bruunhjejle.dk | TXT | Text record | "_globalsign-domain-verification=4mOv23Iz56kxkOQGuK1wommjv-3A_CCu2MlSBWU48Q" |
| www.bruunhjejle.dk | TXT | Text record | "_globalsign-domain-verification=EbWxL0C3HIyakrAlsz-4XZrY-gI05xMMOQ43BTG5ms" |
| www.bruunhjejle.dk | TXT | Text record | "_globalsign-domain-verification=JeMlIrLwGWzK_LB3ZI9ReIDU5HsjATJm9QKkPIuolc" |
| www.bruunhjejle.dk | TXT | Text record | "_globalsign-domain-verification=RajPI3r72W3aH8N2HNHFWl0adYjiqFekkCPfjQ2GYn" |
| www.bruunhjejle.dk | TXT | Text record | "ItQnHoptxFq5XZmQSbU2JyE1U6n/GTLa0rpO5fSp16s5iWyMsHt9PyqEiwX8Ijz98kL2X2Q4mVOSv71o1P7LxQ==" |
| www.bruunhjejle.dk | SPF | Sender Policy Framework | "v=spf1 include:spf1.bruunhjejle.dk include:spf2.bruunhjejle.dk -all" |
| www.bruunhjejle.dk | CNAME | Canonical name | bruunhjejle.dk |
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 |
|---|---|
| Drupal 10 | CMS |
| PHP | Programming languages |
| Nginx | Web servers, Reverse proxies |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
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 2.6.32 | 94% |
Vulnerability description
OS Detection