Vulnerability Scan Result
| Title: | Arizona Public Service |
| Description: | APS is among the nation’s top energy companies for reliable service. |
| ip_address | 45.60.1.218 |
| country | US  |
| network_name | Incapsula Inc |
| asn | AS19551 |
21/tcp | ftp | - - |
25/tcp | smtp | - - |
37/tcp | time | - - |
43/tcp | whois | - - |
53/tcp | domain | - - |
80/tcp | https | - - |
81/tcp | hosts2-ns | - - |
88/tcp | kerberos-sec | - - |
110/tcp | pop3 | - - |
119/tcp | nntp | - - |
135/tcp | msrpc | - - |
139/tcp | netbios-ssn | - - |
143/tcp | imap | - - |
389/tcp | ldap | - - |
443/tcp | https | - - |
444/tcp | snpp | - - |
465/tcp | smtps | - - |
514/tcp | shell | - - |
543/tcp | klogin | - - |
554/tcp | rtsp | - - |
587/tcp | submission | - - |
631/tcp | ipp | - - |
990/tcp | ftps | - - |
993/tcp | imaps | - - |
995/tcp | pop3s | - - |
1025/tcp | NFS-or-IIS | - - |
1028/tcp | other | - - |
1029/tcp | ms-lsa | - - |
1080/tcp | socks | - - |
1194/tcp | openvpn | - - |
1337/tcp | waste | - - |
1433/tcp | ms-sql-s | - - |
1701/tcp | l2f | - - |
1720/tcp | h323q931 | - - |
2000/tcp | cisco-sccp | - - |
2001/tcp | dc | - - |
2002/tcp | globe | - - |
2049/tcp | nfs | - - |
2078/tcp | tpcsrvr | - - |
2080/tcp | autodesk-nlm | - - |
2082/tcp | infowave | - - |
2083/tcp | radsec | - - |
2086/tcp | gnunet | - - |
2087/tcp | eli | - - |
2100/tcp | amiganetfs | - - |
2121/tcp | ccproxy-ftp | - - |
2222/tcp | EtherNetIP-1 | - - |
2967/tcp | symantec-av | - - |
3000/tcp | ppp | - - |
3050/tcp | gds_db | - - |
3306/tcp | mysql | - - |
3389/tcp | ms-wbt-server | - - |
3690/tcp | svn | - - |
4280/tcp | vrml-multi-use | - - |
4333/tcp | msql | - - |
4444/tcp | krb524 | - - |
4445/tcp | upnotifyp | - - |
5000/tcp | upnp | - - |
5004/tcp | avt-profile-1 | - - |
5005/tcp | avt-profile-2 | - - |
5009/tcp | airport-admin | - - |
5051/tcp | ida-agent | - - |
5060/tcp | sip | - - |
5222/tcp | xmpp-client | - - |
5223/tcp | hpvirtgrp | - - |
5631/tcp | pcanywheredata | - - |
5800/tcp | vnc-http | - - |
5900/tcp | vnc | - - |
5901/tcp | vnc-1 | - - |
5985/tcp | wsman | - - |
5986/tcp | wsmans | - - |
6000/tcp | X11 | - - |
6001/tcp | X11:1 | - - |
6379/tcp | redis | - - |
6699/tcp | napster | - - |
7000/tcp | afs3-fileserver | - - |
7001/tcp | afs3-callback | - - |
7070/tcp | realserver | - - |
8000/tcp | https | - - |
8008/tcp | https | - - |
8009/tcp | ajp13 | - - |
8080/tcp | https | - - |
8081/tcp | blackice-icecap | - - |
8200/tcp | trivnet1 | - - |
8222/tcp | other | - - |
8443/tcp | https-alt | - - |
8500/tcp | fmtp | - - |
8888/tcp | sun-answerbook | - - |
9000/tcp | cslistener | - - |
9042/tcp | other | - - |
9100/tcp | jetdirect | - - |
9800/tcp | davsrc | - - |
9999/tcp | abyss | - - |
10000/tcp | snet-sensor-mgmt | - - |
20000/tcp | dnp | - - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Babel | Miscellaneous |
| Font Awesome | Font scripts |
| Bootstrap 3.3.7 | UI frameworks |
| PubSubJS | JavaScript libraries |
| core-js 2.5.5 | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery 3.3.1 | JavaScript libraries |
| Windows Server | Operating systems |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| DoubleClick Floodlight | Advertising |
| Webpack | Miscellaneous |
| WordPress | CMS, Blogs |
| Microsoft ASP.NET | Web frameworks |
| DigiCert | SSL/TLS certificate authorities |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Hotjar | Analytics |
| IIS 10.0 | Web servers |
| Imperva | Security, CDN |
| Qualtrics | Surveys |
| HSTS | Security |
| Sitecore | CMS |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.439 | 0.97574 | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2020-11022 | 6.9 | 0.02391 | 0.85196 | In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. |
| CVE-2019-11358 | 6.1 | 0.02362 | 0.85104 | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. |
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 | Cookie Name | Evidence |
|---|---|---|
| https://www.aps.com/en/residential/home | visid_incap_2153711 | Set-Cookie: .aps.com |
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 | Cookie Name | Evidence |
|---|---|---|
| https://www.aps.com/en/residential/home | website#lang, shell#lang, incap_ses_691_2153711 | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: website#lang=en Set-Cookie: shell#lang=en Set-Cookie: incap_ses_691_2153711=eWx9Vj8VlXseoeBT5eyWCUNBCWoAAAAA0WDRpbusi1NNA/isiKwy+g== |
Vulnerability description
We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.
Recommendation
Ensure that the HttpOnly flag is set for all cookies.
Classification
| CWE | CWE-1004 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2024-6484 | 6.4 | 0.00049 | 0.15167 | A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser. |
| CVE-2019-8331 | 6.1 | 0.01668 | 0.823 | In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute. |
| CVE-2018-20677 | 6.1 | 0.09999 | 0.93138 | In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. |
| CVE-2018-20676 | 6.1 | 0.05658 | 0.90464 | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. |
| CVE-2018-14042 | 6.1 | 0.02281 | 0.84855 | In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. |
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
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 | Evidence |
|---|---|
| https://www.aps.com/en/residential/home | 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
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| Babel | Miscellaneous |
| Font Awesome | Font scripts |
| Bootstrap 3.3.7 | UI frameworks |
| PubSubJS | JavaScript libraries |
| core-js 2.5.5 | JavaScript libraries |
| Google Analytics | Analytics |
| jQuery 3.3.1 | JavaScript libraries |
| Windows Server | Operating systems |
| MySQL | Databases |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| React | JavaScript frameworks |
| DoubleClick Floodlight | Advertising |
| Webpack | Miscellaneous |
| WordPress | CMS, Blogs |
| Microsoft ASP.NET | Web frameworks |
| DigiCert | SSL/TLS certificate authorities |
| reCAPTCHA | Security |
| Google Tag Manager | Tag managers |
| Hotjar | Analytics |
| IIS 10.0 | Web servers |
| Imperva | Security, CDN |
| Qualtrics | Surveys |
| HSTS | Security |
| Sitecore | CMS |
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.aps.com/en/residential/home | 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
| URL | Evidence |
|---|---|
| https://www.aps.com/en/residential/home | 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 |
Infrastructure Vulnerabilities
Evidence
We managed to detect a publicly accessible Virtual Network Computing (VNC) service. PORT STATE SERVICE VERSION 5800/tcp open vnc-http
Vulnerability description
We found that the Virtual Network Computing (VNC) service is publicly accessible. VNC, widely used for remote desktop access, enables users to remotely view and interact with a computer's desktop environment. This capability makes it a prime target for attackers.
Risk description
The risk exists that by exploiting this service, an attacker could launch an authentication attack that can lead to unauthorized access and control over network resources.
Recommendation
We recommend turning off VNC access over the public Internet and instead using a Virtual Private Network (VPN) that mandates two-factor authentication (2FA). If the VNC service is essential for business purposes, limiting access to designated IP addresses is recommended.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.aps.com | A | IPv4 address | 45.60.1.218 |
| www.aps.com | CNAME | Canonical name | 2nxhzfo.x.incapdns.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.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | SSL/TLS certificate authorities |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| 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
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Operating System | Accuracy |
|---|---|
| Windows | 100% |
Vulnerability description
OS Detection
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.
Evidence
| Software / Version | Category |
|---|---|
| Sitecore | CMS |
| WordPress | CMS, Blogs |
| MySQL | Databases |
| PHP | Programming languages |
| Windows Server | Operating systems |
| Microsoft ASP.NET | Web frameworks |
| Amazon Web Services | PaaS |
| React | JavaScript frameworks |
| IIS 10.0 | Web servers |
| Qualtrics | Surveys |
| jQuery | JavaScript libraries |
| Hotjar | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| DoubleClick Floodlight | Advertising |
| reCAPTCHA | Security |
| Imperva | Security, CDN |
| HSTS | Security |
| DigiCert | 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.