Vulnerability Scan Result
| Title: | DATEV | Führend in Software, Service & Wissen. |
| Description: | Unterstützung für Steuerberatung, Wirtschaftsprüfung, Rechtsberatung, Unternehmen & den öffentlichen Sektor. |
| ip_address | 193.27.50.202 |
| country | DE  |
| network_name | DATEV eG |
| asn | AS15451 |
80/tcp | http | - - |
443/tcp | http | Apache httpd - |
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Adobe Dynamic Media Classic | Digital asset management |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Adobe Experience Platform Launch | Tag managers |
| Adobe Client Data Layer 2.0.2 | JavaScript frameworks |
| Java | Programming languages |
| lit-element 4.2.1 | JavaScript libraries |
| Open Graph | Miscellaneous |
| Google Ads Conversion Tracking | Analytics |
| Adobe Experience Manager | CMS |
| OneTrust | Cookie compliance |
| HSTS | Security |
| Thawte | SSL/TLS certificate authorities |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://www.datev.de/web/de | TASF12e63f4e | Set-Cookie: .www.datev.de |
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 | Evidence |
|---|---|
| https://www.datev.de/web/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
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
| Software / Version | Category |
|---|---|
| Google Ads | Advertising |
| Adobe Dynamic Media Classic | Digital asset management |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Adobe Experience Platform Launch | Tag managers |
| Adobe Client Data Layer 2.0.2 | JavaScript frameworks |
| Java | Programming languages |
| lit-element 4.2.1 | JavaScript libraries |
| Open Graph | Miscellaneous |
| Google Ads Conversion Tracking | Analytics |
| Adobe Experience Manager | CMS |
| OneTrust | Cookie compliance |
| HSTS | Security |
| Thawte | 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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://www.datev.de/web/de | 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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.datev.de/web/de/marktplatz | GET | Query: utm_author=intern utm_campaignid=datev-de utm_content=datev-marktplatz utm_medium=footer utm_target=neutral 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 Cookies: TASF12e63f4e=123adfa... | Operating system paths found in the HTTP response: |
| https://www.datev.de/web/de/shop | GET | Query: utm_author=intern utm_campaignid=datev-de utm_content=shop utm_medium=big-picture utm_target=alle 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 Cookies: TASF12e63f4e=123adfa924c55ec61... | Operating system paths found in the HTTP response: |
Vulnerability description
We found operating system paths returned in a HTTP response.
Risk description
The risk is that path disclosure may help an attacker learn more about the remote server's file system, thus increasing the effectiveness and precision of any future attacks.
Recommendation
Configure the web server to avoid leaking path information by using generic error messages that do not reveal any internal file paths. Make sure no server file is referred with its absolute path in the website code.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.datev.de/web/de/berufsgruppenuebergreifend/presse | GET | Query: utm_author=intern utm_campaignid=datev-de utm_content=presse utm_medium=footer utm_target=neutral 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 Cookies: TASF12e63f4e=123adfa924c55ec61... |
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 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.datev.de | A | IPv4 address | 193.27.50.202 |
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 |
|---|---|
| Adobe Experience Manager | CMS |
| Java | Programming languages |
| Adobe Dynamic Media Classic | Digital asset management |
| Adobe Client Data Layer 2.0.2 | JavaScript frameworks |
| Google Ads | Advertising |
| OneTrust | Cookie compliance |
| lit-html 3.3.1 | JavaScript libraries |
| lit-element 4.2.1 | JavaScript libraries |
| Adobe Experience Platform Launch | Tag managers |
| Google Ads Conversion Tracking | Analytics |
| Linkedin Insight Tag | Analytics |
| Linkedin Ads | Advertising |
| Thawte | SSL/TLS certificate authorities |
| HSTS | Security |
| 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.