Vulnerability Scan Result
| Title: | |
| Description: | No description found |
| ip_address | 103.208.248.156 |
| country | IN  |
| network_name | Axis Bank Limited |
| asn | AS135086 |
443/tcp | https | Microsoft HTTPAPI httpd 2 |
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Facebook Pixel 2.9.216 | Analytics |
| Bootstrap | UI frameworks |
| Google Analytics UA | Analytics |
| jQuery | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Quora Pixel | Analytics |
| Priority Hints | Performance |
| Microsoft ASP.NET | Web frameworks |
| Dynatrace | Analytics |
| Dynatrace RUM | RUM |
| Google Tag Manager | Tag managers |
| HSTS | Security |
Web Application Vulnerabilities
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx | dtCookie2f4io6rn | Set-Cookie: .axisbank.co.in |
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://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx | ASP.NET_SessionId, ASP.NET_SessionID_AXDCFT2E6767UCK, ASP.NET_SessionID_AXDCFT2E676NPF1, ASP.NET_SessionID_AXDCFT2E676NPF2, ASP.NET_SessionID_AXDCFT2E6767RFH, ASP.NET_SessionID_AXDCFT2E6767QWE, ASP.NET_SessionID_QO22TPON4CAL45LNRI, ASP.NET_SessionID_AXDCFT2E6767WDS, ASP.NET_SessionID_A67O378T520REG3NRI, dtCookie2f4io6rn | Set-Cookie: ASP.NET_SessionId=q2epuwohh00irkyrrtethuzr Set-Cookie: ASP.NET_SessionID_AXDCFT2E6767UCK=A Set-Cookie: ASP.NET_SessionID_AXDCFT2E676NPF1= Set-Cookie: ASP.NET_SessionID_AXDCFT2E676NPF2= Set-Cookie: ASP.NET_SessionID_AXDCFT2E6767RFH= Set-Cookie: ASP.NET_SessionID_AXDCFT2E6767QWE= Set-Cookie: ASP.NET_SessionID_QO22TPON4CAL45LNRI=0 Set-Cookie: ASP.NET_SessionID_AXDCFT2E6767WDS= Set-Cookie: ASP.NET_SessionID_A67O378T520REG3NRI=0 Set-Cookie: dtCookie2f4io6rn=v_4_srv_3_sn_4C949803644EA6871405AEF0946419A4_perc_0_ol_1_app-3Aea7c4b59f27d43eb_0 |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx | dtCookie2f4io6rn | The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: dtCookie2f4io6rn=v_4_srv_3_sn_4C949803644EA6871405AEF0946419A4_perc_0_ol_1_app-3Aea7c4b59f27d43eb_0 |
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
| URL | Evidence |
|---|---|
| https://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx | 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://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx | 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-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Microsoft Advertising | Advertising |
| Linkedin Ads | Advertising |
| Linkedin Insight Tag | Analytics |
| Facebook Pixel 2.9.216 | Analytics |
| Bootstrap | UI frameworks |
| Google Analytics UA | Analytics |
| jQuery | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Quora Pixel | Analytics |
| Priority Hints | Performance |
| Microsoft ASP.NET | Web frameworks |
| Dynatrace | Analytics |
| Dynatrace RUM | RUM |
| Google Tag Manager | Tag managers |
| HSTS | Security |
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
Website is accessible.
Evidence
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx | GET | Query: utm_source=branch 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: digital.nri@axisbank.com |
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.
Evidence
| URL | Evidence |
|---|---|
| https://application.axisbank.co.in/webforms/NRI_NEW_ONLINE_APPLICATION_FORM/NRILogin.aspx |
|
Vulnerability description
We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.
Risk description
The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.
Recommendation
Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| application.axisbank.co.in | A | IPv4 address | 103.208.248.156 |
| application.axisbank.co.in | AAAA | IPv6 address | 2403:0:500:11::282 |
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 |
|---|---|
| Microsoft ASP.NET | Web frameworks |
| YouTube | Video players |
| Bootstrap | UI frameworks |
| Dynatrace | Analytics |
| Google Tag Manager | Tag managers |
| Google Analytics | Analytics |
| Dynatrace RUM | RUM |
| HSTS | Security |
| Select2 | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Modernizr | JavaScript libraries |
| jQuery | JavaScript libraries |
| Dynamics.js | JavaScript libraries |
| Linkedin Ads | Advertising |
| Cloudflare | CDN |
| Font Awesome 5.15.3 | Font scripts |
| cdnjs | CDN |
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.