Vulnerability Scan Result

| Title: | La Opinión A Coruña, noticias de A Coruña, Galicia, España y el mundo |
| Description: | Noticias de la ciudad de A Coruña con La Opinión A Coruña, Oleiros, Sada, Arteixo, Cambre, Culleredo, Betanzos.. y todos los concellos del área metropolitana con http://laopinioncoruna.es . Información de actualidad sobre Galicia, España, el mundo, economía, cultura,... Última hora del Deportivo, Liceo y todo el deporte local. Las mejores entrevistas y los mejores artículos de opinión. |
| ip_address | 199.232.194.133 |
| country | US |
| network_name | Fastly, Inc. |
| asn | AS54113 |
| ip_address | 199.232.198.133 |
| country | US |
| network_name | Fastly, Inc. |
| asn | AS54113 |
80/tcp | http | Varnish - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Amazon Advertising | Advertising |
| Google Publisher Tag | Advertising |
| FancyBox 3.5.7 | JavaScript libraries |
| Google Font API | Font scripts |
| core-js 3.44.0 | JavaScript libraries |
| GLS | Shipping carriers |
| ID5 1.0.97 | Advertising |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.14.1 | JavaScript libraries |
| MySQL | Databases |
| Nuxt.js | JavaScript frameworks, Web frameworks, Static site generator |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Piano | Personalisation |
| Pinia | JavaScript libraries |
| Preact | JavaScript libraries |
| Prebid 10.29.1 | Advertising |
| DoubleClick Floodlight | Advertising |
| Swiper | JavaScript libraries |
| Utiq | Advertising |
| Vue.js | JavaScript frameworks |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Cxense | Personalisation, Segmentation |
| Didomi | Cookie compliance |
| Google AdSense | Advertising |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Marfeel | Analytics, Advertising |
| Max Mega Menu | Widgets, WordPress plugins |
| HSTS | Security |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.laopinioncoruna.es/ | 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
| URL | Evidence |
|---|---|
| https://www.laopinioncoruna.es/ | 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-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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.laopinioncoruna.es/ | 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 | Credit Card Number: 4673227357197067 |
Vulnerability description
We noticed that this application does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. Sensitive data targeted usually consists of emails, credit card and social security numbers.
Risk description
The risk exists that sensitive personal information within the application could be accessed by unauthorized parties. This could lead to privacy violations, identity theft, or other forms of personal or corporate harm.
Recommendation
Compartmentalize the application to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-201 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.laopinioncoruna.es/buzzeando/ | 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 | Different hostname found for a source file |
| https://www.laopinioncoruna.es/finanzas-personales/ | 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 | Different hostname found for a source file |
Vulnerability description
We have noticed that the target application includes scripts from external domains. This may be problematic as such scripts have the same level of access as the application's own scripts, which means they can interact with application data and perform actions as the current user.
Risk description
The risk is that cross domain file inclusion can lead to a wide variety security breaches if the external scripts are malicious or become compromised.
Recommendation
You do not have any control over what is in that code. Ensure files on the site are loaded from only trusted sources.
Classification
| CWE | CWE-829 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Amazon Advertising | Advertising |
| Google Publisher Tag | Advertising |
| FancyBox 3.5.7 | JavaScript libraries |
| Google Font API | Font scripts |
| core-js 3.44.0 | JavaScript libraries |
| GLS | Shipping carriers |
| ID5 1.0.97 | Advertising |
| jQuery 3.7.1 | JavaScript libraries |
| jQuery UI 1.14.1 | JavaScript libraries |
| MySQL | Databases |
| Nuxt.js | JavaScript frameworks, Web frameworks, Static site generator |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Piano | Personalisation |
| Pinia | JavaScript libraries |
| Preact | JavaScript libraries |
| Prebid 10.29.1 | Advertising |
| DoubleClick Floodlight | Advertising |
| Swiper | JavaScript libraries |
| Utiq | Advertising |
| Vue.js | JavaScript frameworks |
| Priority Hints | Performance |
| WordPress | CMS, Blogs |
| Cxense | Personalisation, Segmentation |
| Didomi | Cookie compliance |
| Google AdSense | Advertising |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Marfeel | Analytics, Advertising |
| Max Mega Menu | Widgets, WordPress plugins |
| HSTS | Security |
| Cart Functionality | Ecommerce |
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 | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.laopinioncoruna.es/ | 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: estrategia.digital@pi360.es |
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 |
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
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Cart Functionality | Ecommerce |
| WordPress | CMS, Blogs |
| Nuxt.js | JavaScript frameworks, Web frameworks, Static site generator |
| MySQL | Databases |
| PHP | Programming languages |
| GLS | Shipping carriers |
| Vue.js | JavaScript frameworks |
| Pinia | JavaScript libraries |
| Cxense | Personalisation, Segmentation |
| Prebid 10.29.1 | Advertising |
| Piano | Personalisation |
| Marfeel | Analytics, Advertising |
| ID5 1.0.97 | Advertising |
| Google Tag Manager | Tag managers |
| Google AdSense | Advertising |
| core-js 3.44.0 | JavaScript libraries |
| Priority Hints | Performance |
| Preact | JavaScript libraries |
| Max Mega Menu | Widgets, WordPress plugins |
| reCAPTCHA | Security |
| Utiq | Advertising |
| Google Publisher Tag | Advertising |
| Didomi | Cookie compliance |
| DoubleClick Floodlight | Advertising |
| Amazon Advertising | Advertising |
| HSTS | Security |
| Open Graph | Miscellaneous |
| jQuery UI 1.14.1 | JavaScript libraries |
| jQuery 3.7.1 | JavaScript libraries |
| FancyBox 3.5.7 | JavaScript libraries |
| Google Font API | Font scripts |
| Swiper | JavaScript libraries |
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 |
|---|---|
| Crestron XPanel control system | 89% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.laopinioncoruna.es | A | IPv4 address | 199.232.194.133 |
| www.laopinioncoruna.es | A | IPv4 address | 199.232.198.133 |
| www.laopinioncoruna.es | CNAME | Canonical name | prensaiberica.map.fastly.net |
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.
