Vulnerability Scan Result
| Title: | RBC Royal Bank |
| Description: | No description found |
| ip_address | 142.245.66.147 |
| country | CA  |
| network_name | Royal Bank of Canada |
| asn | AS16730 |
443/tcp | https | IBM WebSEAL reverse http proxy - |
| Software / Version | Category |
|---|---|
| Bootstrap | UI frameworks |
| Java | Programming languages |
| JavaServer Faces | Web frameworks |
| jQuery | JavaScript libraries |
| DigiCert | SSL/TLS certificate authorities |
| Java Servlet | Web frameworks |
| HSTS | Security |
| JSP | Web frameworks |
Web Application Vulnerabilities
Vulnerability description
We found that the target application's web server presents an SSL/TLS certificate that is not trusted by web browsers. This issue typically arises when the server uses a self-signed certificate, a certificate from an untrusted authority, or a certificate that has expired or is invalid for other reasons. The lack of a trusted certificate makes it challenging for users to verify the authenticity of the server, undermining the security of the SSL/TLS connection.
Risk description
The risk is that an attacker could easily mount a man-in-the-middle attack in order to sniff the SSL communication by presenting the user a fake SSL certificate.
Recommendation
We recommend you to configure a trusted SSL certificate for the web server. Examples of how to configure SSL for various servers for Apache and Nginx are referenced.
Classification
| CWE | CWE-295 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Bootstrap | UI frameworks |
| Java | Programming languages |
| JavaServer Faces | Web frameworks |
| jQuery | JavaScript libraries |
| DigiCert | SSL/TLS certificate authorities |
| Java Servlet | Web frameworks |
| HSTS | Security |
| JSP | Web frameworks |
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://142.245.66.147/webapp/ukv0/signin/logon.xhtml | 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 | Evidence |
|---|---|
| https://142.245.66.147/webapp/ukv0/signin/logon.xhtml | 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 | Method | Summary |
|---|---|---|
| https://142.245.66.147/webapp/ukv0/signin/logon.xhtml?__proto__[crVsaSZqMnW4EqBoI22emA]=crVsaSZqMnW4EqBoI22emA1&__proto__.crVsaSZqMnW4EqBoI22emA=crVsaSZqMnW4EqBoI22emA3&__proto__[crVsaSZqMnW4EqBoI22emA]=crVsaSZqMnW4EqBoI22emA2&constructor.prototype.crVsaSZqMnW4EqBoI22emA=crVsaSZqMnW4EqBoI22emA5&constructor.prototype[crVsaSZqMnW4EqBoI22emA]=crVsaSZqMnW4EqBoI22emA4&constructor[prototype][crVsaSZqMnW4EqBoI22emA]= | OPTIONS | We did a HTTP OPTIONS request. The server responded with a 200 status code and the header: `Allow: ` 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 |
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Java | Programming languages |
| Bootstrap | UI frameworks |
| JSP | Web frameworks |
| Java Servlet | Web frameworks |
| HSTS | Security |
| DigiCert | SSL/TLS certificate authorities |
| jQuery | 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.